Juniper Networks Junos OS
Junos OS and Junos OS Evolved: Improper OSPF LSA validation causes an rpd crash when prefix-SID best-route installation is used
Edge device · Router / network deviceknown edge product: Juniper Networks Junos OS Junos OS and Junos (high confidence)
A Reachable Assertion vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an adjacent OSPF peer to cause a denial of service via OSPF traffic processed while OSPF Source Packet Routing best-route Prefix-SID installation is configured.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 23.2R2-S7.7
- >= 23.4, < 23.4R2-S8.13
- >= 24.2, < 24.2R2-S5.5
- >= 24.4, < 24.4R2-S5
- >= 25.2, < 25.2R2-S2
- >= 25.4, < 25.4R1-S3
- >= 26.2, < 26.2R1-S2
Fixed in 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3, 26.2R1-S2
- < 23.2R2-S7.7-EVO
- >= 23.4, < 23.4R2-S8.11-EVO
- >= 24.2, < 24.2R2-S5.6-EVO
- >= 24.4, < 24.4R2-S5-EVO
- >= 25.2, < 25.2R2-S2-EVO
- >= 25.4, < 25.4R1-S3-EVO
- >= 26.2, < 26.2R1-S2-EVO
- 23.4X100
- >= 25.2X100, < 25.2X100-D35-EVO
- >= 25.4X300, < 25.4X300-D40-EVO
Fixed in 23.2R2-S7.7-EVO, 23.4R2-S8.11-EVO, 24.2R2-S5.6-EVO, 24.4R2-S5-EVO, 25.2R2-S2-EVO, 25.4R1-S3-EVO, 26.2R1-S2-EVO, 25.2X100-D35-EVO, 25.4X300-D40-EVO
Mitigation
The following software releases have been updated to resolve this specific issue: Junos OS: 23.2R2-S7.7, 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3, 25.4R2, 26.2R1-S2, 26.2R2, 26.4R1, and all subsequent releases. Junos OS Evolved: 23.2R2-S7.7-EVO, 23.4R2-S8.11-EVO, 24.2R2-S5.6-EVO, 24.4R2-S5-EVO, 25.2R2-S2-EVO, 25.2X100-D35-EVO, 25.4R1-S3-EVO, 25.4R2-EVO, 25.4X300-D40-EVO, 26.2R1-S2-EVO, 26.2R2-EVO, 26.4R1-EVO, and all subsequent releases. Note: For Junos OS releases 23.2, 23.4, and 24.2, and Junos OS Evolved releases 23.2-EVO, 23.4-EVO, and 24.2-EVO, specific respins have been referenced. Previously published versions of these releases have been rebuilt to resolve the security vulnerabilities identified in this advisory.
Workaround
If OSPF packet processing on an enabled interface isn't needed, but it has just been configured so that it's added to the LSDB, ensure it's configured as 'passive': [ protocols ospf area <area> interface <interface> passive ]
References
- Vendor advisory supportportal.juniper.net/JSA112187
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.