Junos OS Evolved: A port which has been inadvertently exposed can be reached by an attacker
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 23.2R2-S7-EVO, 23.4R2-S8-EVO, 24.2R2-S5-EVO, 24.4R2-S4-EVO, 25.2R2-S1-EVO, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a limited information disclosure and availability impact to the device. Due to a wrong initialization, a process which should only be able to communicate internally within the device can be reached over the network via an open port. This leads to a device being inadvertently exposed and increased CPU cycles spent processing ingress packets. This issue affects Junos OS Evolved: • all versions before 23.2R2-S7-EVO, • 23.4 versions before 23.4R2-S8-EVO, • 24.2 versions before 24.2R2-S5-EVO, • 24.4 versions before 24.4R2-S4-EVO, • 25.2 versions before 25.2R2-S1-EVO, • 25.4 versions before 25.4R1-S2-EVO.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS Evolved
fixed in 23.2R2-S7-EVO; From 23.4 · fixed in 23.4R2-S8-EVO; From 24.2 · fixed in 24.2R2-S5-EVO; From 24.4 · fixed in 24.4R2-S4-EVO; From 25.2 · fixed in 25.2R2-S1-EVO; From 25.4 · fixed in 25.4R1-S2-EVO