Junos OS and Junos OS Evolved: BGP update message containing aggregator attribute with an ASN value of zero (0) is accepted
- 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 21.4R3-S6, 22.2R3-S3, 22.4R3, 21.4R3-S7-EVO, 22.2R3-S4-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 Check for Unusual or Exceptional Conditions vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause an integrity impact to the downstream devices. When a peer sends a BGP update message which contains the aggregator attribute with an ASN value of zero (0), rpd accepts and propagates this attribute, which can cause issues for downstream BGP peers receiving this. This issue affects: Junos OS: • All versions before 21.4R3-S6, • 22.2 versions before 22.2R3-S3, • 22.4 versions before 22.4R3; Junos OS Evolved: • All versions before 21.4R3-S7-EVO, • 22.2 versions before 22.2R3-S4-EVO, • 22.4 versions before 22.4R3-EVO.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Juniper Networks Junos OS
fixed in 21.4R3-S6; From 22.2 · fixed in 22.2R3-S3; From 22.4 · fixed in 22.4R3
- Juniper Networks Junos OS Evolved
fixed in 21.4R3-S7-EVO; From 22.2 · fixed in 22.2R3-S4-EVO; From 22.4 · fixed in 22.4R3-EVO