JunosE 9.2
JUNOSE-9.2Juniper · OS release · JunosE Series
Unsupported since · 5953 days ago
JunosE 9.2 reached end of support on (5953 days ago).
- Notice published
- 18y 4mo ago
- End of software maintenance
- 16y 12mo ago
- End of security support
- 16y 12mo ago
- End of support
- 16y 4mo ago
Lifecycle Milestones
| Lifecycle notice published | 18y 4mo ago | |
|---|---|---|
| End of software maintenance | 16y 12mo ago | |
| End of security vulnerability support | 16y 12mo ago | |
| Last date of support | 16y 4mo ago |
Known Exploited Vulnerabilities
7 CVEs in CISA's Known Exploited Vulnerabilities catalog are recorded against the Juniper platform this release belongs to and may apply to this release; verify against the vendor advisory before acting. Juniper security vulnerability support for this release stopped on . Where one applies, upgrade, isolate, or compensate.
| CVE | KEV added | Vulnerability | Flags |
|---|---|---|---|
CVE-2025-21590
|
Juniper Junos OS Improper Isolation or Compartmentalization Vulnerability
KEV added 2025-03-13
|
||
CVE-2023-36844
|
Juniper Junos OS EX Series PHP External Variable Modification Vulnerability
KEV added 2023-11-13
|
||
CVE-2023-36845
|
Juniper Junos OS EX Series and SRX Series PHP External Variable Modification Vulnerability
KEV added 2023-11-13
|
||
CVE-2023-36846
|
Juniper Junos OS SRX Series Missing Authentication for Critical Function Vulnerability
KEV added 2023-11-13
|
||
CVE-2023-36847
|
Juniper Junos OS EX Series Missing Authentication for Critical Function Vulnerability
KEV added 2023-11-13
|
||
CVE-2023-36851
|
Juniper Junos OS SRX Series Missing Authentication for Critical Function Vulnerability
KEV added 2023-11-13
|
||
CVE-2020-1631
|
Juniper Junos OS Path Traversal Vulnerability
KEV added 2022-03-25
|
Source: CISA Known Exploited Vulnerabilities catalog. The Ransomware flag reflects CISA's own knownRansomwareCampaignUse field, set when the CVE has been observed in ransomware campaigns per their threat intel. It's not a property of the vulnerability description itself.
Correlation is at the platform level, not per-OS-version (entries disclosed well before this release train shipped are left out). Not exhaustive: KEV only lists actively-exploited CVEs and many relevant unexploited vulnerabilities are not here. Verify against vendor security advisories (PSIRT, JSA, PAN-SA) and NVD before acting. See compensating controls if refresh isn't immediate.
Is JunosE 9.2 still maintained?
No. Juniper no longer maintains JunosE 9.2; support ended on 2010-07-24. It receives no fixes of any kind, including security patches. Plan an upgrade to a maintained release. See Juniper's lifecycle bulletin.
When do security fixes for JunosE 9.2 stop?
Juniper stopped engineering fixes for JunosE 9.2, including security patches, on 2009-11-24. A device on this release cannot be patched against vulnerabilities disclosed after that date without upgrading.
What should I upgrade JunosE 9.2 to?
Upgrade to a currently maintained Juniper release. Check Juniper's release notes for the recommended version.
Which known-exploited CVEs may apply to the JunosE 9.2?
7 CVEs in CISA's Known Exploited Vulnerabilities catalog are recorded against Juniper JunosE and may apply to JunosE 9.2, whose security fixes stopped on 2009-11-24. Verify each against the vendor advisory for the fixed releases before acting. See the Known Exploited Vulnerabilities table for the full list.
JunosE 9.2 Release Lifecycle
JunosE 9.2 is a Juniper JunosE software release. Releases are maintained on a fixed schedule: Juniper ships fixes and security patches until the release reaches end of engineering, after which a device must be upgraded to a maintained release to stay patchable. The dates below are milestones for the software train, not for any specific appliance — hardware running this release has its own separate lifecycle. This product has reached end of life as of , meaning Juniper no longer provides technical support, software updates, or hardware replacement for this product. Organizations still running the JunosE 9.2 should plan a migration .