Routing-service crash via malformed BGP flowspec update
Published Apr 17, 2023 · Updated Feb 6, 2025
Improper length handling in Juniper Networks Junos OS and Junos OS Evolved allows remote attackers to crash RPD with a BGP flowspec update. The routing protocol daemon mishandles inconsistent length information in a malformed BGP flowspec update and terminates while processing it. The device must receive BGP flowspec updates; repeated delivery sustains the routing-service interruption without exposing or altering data.
Summary
What happened
Improper length handling in Juniper Networks Junos OS and Junos OS Evolved allows remote attackers to crash RPD with a BGP flowspec update. The routing protocol daemon mishandles inconsistent length information in a malformed BGP flowspec update and terminates while processing it. The device must receive BGP flowspec updates; repeated delivery sustains the routing-service interruption without exposing or altering data.
The record
- CVE
- CVE-2023-28964
- Published
- Apr 17, 2023
- Updated
- Feb 6, 2025
- Vendor
- Juniper Networks
- Product
- Junos OS Evolved
- Classifications
- CWE-130, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=20.2 <20.2R2-EVO
- Affected versionversion=20.3 <20.3R2-EVO
- Affected versionversion=unspecified <20.1R3-EVO
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo