CVE-2024-39541: Junos OS and Junos OS Evolved: Inconsistent information in the TE database can lead to an rpd crash
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Juniper Networks Junos OS 22.4R3-S1, 23.2R2, 23.4R1-S1, 23.4R2; Juniper Networks Junos OS Evolved 22.4R3-S2-EVO, 23.2R2-EVO, 23.4R1-S1-EVO, 23.4R2-EVO.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Juniper Networks Junos OS 22.4R3-S1, 23.2R2, 23.4R1-S1, 23.4R2; Juniper Networks Junos OS Evolved 22.4R3-S2-EVO, 23.2R2-EVO, 23.4R1-S1-EVO, 23.4R2-EVO or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An Improper Handling of Exceptional Conditions vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS). When conflicting information (IP or ISO addresses) about a node is added to the Traffic Engineering (TE) database and then a subsequent operation attempts to process these, rpd will crash and restart. This issue affects: Junos OS: * 22.4 versions before 22.4R3-S1, * 23.2 versions before 23.2R2, * 23.4 versions before 23.4R1-S1, 23.4R2, This issue does not affect Junos OS versions earlier than 22.4R1. Junos OS Evolved: * 22.4-EVO versions before 22.4R3-S2-EVO, * 23.2-EVO versions before 23.2R2-EVO, * 23.4-EVO versions before 23.4R1-S1-EVO, 23.4R2-EVO, This issue does not affect Junos OS Evolved versions earlier than before 22.4R1.
- Published
- Jul 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 26th percentile
- CWE
- CWE-755
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| juniper | junos | cpe:2.3:o:juniper:junos |
| juniper | junos os evolved | cpe:2.3:o:juniper:junos_os_evolved |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (juniper). Independent of NVD's CPE analysis and usually ahead of it.
Juniper Networks Junos OS
- 22.4 and later · before 22.4R3-S1affected · semver
- 23.2 and later · before 23.2R2affected · semver
- 23.4 and later · before 23.4R1-S1, 23.4R2affected · semver
- before 22.4R1not affected · semver
Juniper Networks Junos OS Evolved
- 22.4-EVO and later · before 22.4R3-S2-EVOaffected · semver
- 23.2-EVO and later · before 23.2R2-EVOaffected · semver
- 23.4-EVO and later · before 23.4R1-S1-EVO, 23.4R2-EVOaffected · semver
- before 22.4R1not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junos22.4
- juniper junos23.2
- juniper junos23.4
- juniper junos os evolved22.4
- juniper junos os evolved23.2
- juniper junos os evolved23.4
Same product
juniper: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36845Junos OS: EX and SRX Series: A PHP vulnerability in J-Web allows an unauthenticated to control an important environment variableKEV98Now
- CVE-2023-36846Junos OS: SRX Series: A vulnerability in J-Web allows an unauthenticated attacker to upload arbitrary filesKEV79This week
- CVE-2023-36844Junos OS: EX Series: A PHP vulnerability in J-Web allows an unauthenticated attacker to control important environment variablesKEV78This week
Published before and after this one in the same product
- ← EarlierCVE-2024-39539Jul 11, 2024 · Junos OS: MX Series: Continuous subscriber logins will lead to a memory leak and eventually an FPC crash24Monitor
- ← EarlierCVE-2024-39540Jul 11, 2024 · Junos OS: SRX Series, and MX Series with SPC3: Specific valid TCP traffic can cause a pfe crash34Monitor
- Later →CVE-2024-39542Jul 11, 2024 · Junos OS and Junos OS Evolved: A malformed CFM packet or specific transit traffic leads to FPC crash34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Juniper Networks Junos OS | 22.4R3-S1 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.2R2 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.4R1-S1, 23.4R2 | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 22.4R3-S2-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 23.2R2-EVO | Vendor (CNA) |
| Juniper Networks Junos OS Evolved | 23.4R1-S1-EVO, 23.4R2-EVO | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-395520 days apartJunos OS and Junos OS Evolved: Malformed BGP UPDATE causes RPD crash34Monitor
- CVE-2024-395551 days apartJunos OS and Junos OS Evolved: Receipt of a specific malformed BGP update causes the session to reset34Monitor
- CVE-2024-3038290 days apartJunos OS and Junos OS Evolved: RPD crash when CoS-based forwarding (CBF) policy is configured34Monitor
- CVE-2024-3952590 days apartJunos OS and Junos OS Evolved: When BGP traceoptions is enabled, receipt of specially crafted BGP packet causes RPD crash34Monitor
- CVE-2024-4749192 days apartJunos OS and Junos OS Evolved: Receipt of a specific malformed BGP path attribute leads to an RPD crash32Monitor
- CVE-2025-52948365 days apartJunos OS: Specific unknown traffic pattern causes FPC and system to crash when packet capturing is enabled32Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0943 · Jul 16, 2024(Juniper Junos OS Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-755 · Improper Handling of Exceptional ConditionsCVSS vector
CVSS:4.0/AV:A/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:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.