CVE-2024-39555
Last modified
CVE-2024-39555 is a high-severity vulnerability rated 8.7/10 on the CVSS scale. An Improper Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker sending a specific malformed BGP update message to cause the session to reset, resulting in a Denial of Service (DoS). Continued receipt and processing of these malformed BGP update messages will create a sustained Denial of Service (DoS) condition. Upon receipt of a BGP update message over an established BGP session containing a specifically malformed tunnel encapsulation attribute, when segment routing is enabled, internal processing of the malformed attributes within the update results in improper parsing of remaining attributes, leading to session reset: BGP SEND Notification code 3 (Update Message Error) subcode 1 (invalid attribute list) Only systems with segment routing enabled are vulnerable to this issue. This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations, and requires a remote attacker to have at least one established BGP session. This issue affects: Junos OS: * All versions before 21.4R3-S8, * from 22.2 before 22.2R3-S4, * from 22.3 before 22.3R3-S3, * from 22.4 before 22.4R3-S3, * from 23.2 before 23.2R2-S1, * from 23.4 before 23.4R1-S2, 23.4R2. Junos OS Evolved: * All versions before 21.4R3-S8-EVO, * from 22.2-EVO before 22.2R3-S4-EVO, * from 22.3-EVO before 22.3R3-S3-EVO, * from 22.4-EVO before 22.4R3-S3-EVO, * from 23.2-EVO before 23.2R2-S1-EVO, * from 23.4-EVO before 23.4R1-S2-EVO, 23.4R2-EVO.. EPSS estimates a 0.50% chance of exploitation in the next 30 days.
Description
An Improper Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (RPD) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker sending a specific malformed BGP update message to cause the session to reset, resulting in a Denial of Service (DoS). Continued receipt and processing of these malformed BGP update messages will create a sustained Denial of Service (DoS) condition. Upon receipt of a BGP update message over an established BGP session containing a specifically malformed tunnel encapsulation attribute, when segment routing is enabled, internal processing of the malformed attributes within the update results in improper parsing of remaining attributes, leading to session reset: BGP SEND Notification code 3 (Update Message Error) subcode 1 (invalid attribute list) Only systems with segment routing enabled are vulnerable to this issue. This issue affects eBGP and iBGP, in both IPv4 and IPv6 implementations, and requires a remote attacker to have at least one established BGP session. This issue affects: Junos OS: * All versions before 21.4R3-S8, * from 22.2 before 22.2R3-S4, * from 22.3 before 22.3R3-S3, * from 22.4 before 22.4R3-S3, * from 23.2 before 23.2R2-S1, * from 23.4 before 23.4R1-S2, 23.4R2. Junos OS Evolved: * All versions before 21.4R3-S8-EVO, * from 22.2-EVO before 22.2R3-S4-EVO, * from 22.3-EVO before 22.3R3-S3-EVO, * from 22.4-EVO before 22.4R3-S3-EVO, * from 23.2-EVO before 23.2R2-S1-EVO, * from 23.4-EVO before 23.4R1-S2-EVO, 23.4R2-EVO.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:A/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Juniper | Junos | < 21.4 |
| Juniper | Junos | 21.4 |
| Juniper | Junos | 22.2 |
| Juniper | Junos | 22.3 |
| Juniper | Junos | 22.4 |
| Juniper | Junos | 23.2 |
| Juniper | Junos | 23.4 |
| Juniper | Junos Os Evolved | < 21.4 |
| Juniper | Junos Os Evolved | 21.4 |
| Juniper | Junos Os Evolved | 22.2 |
| Juniper | Junos Os Evolved | 22.3 |
| Juniper | Junos Os Evolved | 22.4 |
| Juniper | Junos Os Evolved | 23.2 |
| Juniper | Junos Os Evolved | 23.4 |
References
- https://supportportal.juniper.net/JSA83015Mitigation, Vendor Advisory
- https://supportportal.juniper.net/JSA83015Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-39555?
How severe is CVE-2024-39555?
How do I fix CVE-2024-39555?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-3955URL GET parameter "logtime" utilized within the "downloadlog…9.8
- CVE-2024-39550A Missing Release of Memory after Effective Lifetime vulnera…7.1
- CVE-2024-39551An Uncontrolled Resource Consumption vulnerability in the H.…8.7
- CVE-2024-39552An Improper Handling of Exceptional Conditions vulnerability…8.7
- CVE-2024-39553An Exposure of Resource to Wrong Sphere vulnerability in the…6.9
- CVE-2024-39554A Concurrent Execution using Shared Resource with Improper S…8.2
- CVE-2024-39556A Stack-Based Buffer Overflow vulnerability in Juniper Netwo…7
- CVE-2024-39557An Uncontrolled Resource Consumption vulnerability in the …7.1
- CVE-2024-39558An Unchecked Return Value vulnerability in the Routing Proto…7.1
- CVE-2024-39559An Improper Check for Unusual or Exceptional Conditions vuln…8.2
- CVE-2024-3956The Pods – Custom Content Types and Fields plugin for WordPr…5.4
- CVE-2024-39560An Improper Handling of Exceptional Conditions vulnerability…7.1
Are you affected by CVE-2024-39555?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
