CVE-2024-21595: Junos OS: EX4100, EX4400, EX4600, QFX5000 Series: A high rate of specific ICMP traffic will cause the PFE to hang
Noroxi assessment
Priority: Monitor (action score 30/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.53% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Juniper Networks Junos OS 21.4R3-S4, 22.1R3-S3, 22.2R3-S1.
Low priority for now. Upgrade to Juniper Networks Junos OS 21.4R3-S4, 22.1R3-S3, 22.2R3-S1 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 Validation of Syntactic Correctness of Input vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS allows a network-based, unauthenticated attacker to cause a Denial of Service (DoS). If an attacker sends high rate of specific ICMP traffic to a device with VXLAN configured, this causes a deadlock of the PFE and results in the device becoming unresponsive. A manual restart will be required to recover the device. This issue only affects EX4100, EX4400, EX4600, QFX5000 Series devices. This issue affects: Juniper Networks Junos OS * 21.4R3 versions earlier than 21.4R3-S4; * 22.1R3 versions earlier than 22.1R3-S3; * 22.2R2 versions earlier than 22.2R3-S1; * 22.3 versions earlier than 22.3R2-S2, 22.3R3; * 22.4 versions earlier than 22.4R2; * 23.1 versions earlier than 23.1R2.
- Published
- Jan 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-1286
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · juniper
- 7.5
- agree
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 | ex4100 | cpe:2.3:h:juniper:ex4100 |
| juniper | ex4400 | cpe:2.3:h:juniper:ex4400 |
| juniper | ex4600 | cpe:2.3:h:juniper:ex4600 |
| juniper | qfx5100 | cpe:2.3:h:juniper:qfx5100 |
| juniper | qfx5100-96s | cpe:2.3:h:juniper:qfx5100-96s |
| juniper | qfx5110 | cpe:2.3:h:juniper:qfx5110 |
| juniper | qfx5120 | cpe:2.3:h:juniper:qfx5120 |
| juniper | qfx5130 | cpe:2.3:h:juniper:qfx5130 |
| juniper | qfx5200 | cpe:2.3:h:juniper:qfx5200 |
| juniper | qfx5200-32c | cpe:2.3:h:juniper:qfx5200-32c |
| juniper | qfx5200-48y | cpe:2.3:h:juniper:qfx5200-48y |
and 4 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junos21.4
- juniper junos22.1
- juniper junos22.2
- juniper junos22.3
- juniper junos22.4
- juniper junos23.1
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
- 21.4R3 and later · before 21.4R3-S4affected · semver
- 22.1R3 and later · before 22.1R3-S3affected · semver
- 22.2R2 and later · before 22.2R3-S1affected · semver
- 22.3 and later · before 22.3R2-S2, 22.3R3affected · semver
- 22.4 and later · before 22.4R2affected · semver
- 23.1 and later · before 23.1R2affected · semver
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-21591Jan 11, 2024 · Junos OS: SRX Series and EX Series: Security Vulnerability in J-web allows a preAuth Remote Code Execution44Plan
- ← EarlierCVE-2024-21594Jan 11, 2024 · Junos OS: SRX 5000 Series: Repeated execution of a specific CLI command causes a flowd crash22Monitor
- Later →CVE-2024-21596Jan 11, 2024 · Junos OS and Junos OS Evolved: A specific BGP UPDATE message will cause a crash in the backup Routing Engine in NSR-enabled devices21Monitor
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 | 21.4R3-S4 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.1R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R3-S1 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.3R2-S2, 22.3R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R2 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.1R2 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-2159892 days apartJunos OS and Junos OS Evolved: A malformed BGP tunnel encapsulation attribute will lead to an rpd crash34Monitor
- CVE-2024-39542182 days apartJunos OS and Junos OS Evolved: A malformed CFM packet or specific transit traffic leads to FPC crash34Monitor
- CVE-2024-216160 days apartJunos OS: MX Series and SRX Series: Processing of a specific SIP packet causes NAT IP allocation to fail30Monitor
- CVE-2023-28985181 days apartSRX Series and MX Series: An FPC core is observed when IDP is enabled on the device and a specific malformed SSL packet is received30Monitor
- CVE-2023-4420491 days apartJunos OS and Junos OS Evolved: The rpd will crash upon receiving a malformed BGP UPDATE message26Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet 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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1286 · Improper Validation of Syntactic Correctness of InputCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.