CVE-2024-47506: Junos OS: SRX Series: A large amount of traffic being processed by ATP Cloud can lead to a PFE crash
Noroxi assessment
Priority: Monitor (action score 32/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.28% (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.
- Fixed version: Juniper Networks Junos OS 21.3R3-S1, 21.4R3, 22.1R2.
- Severity is disputed: the assigning authority (CNA) scores it 5.9, NVD 8.2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Juniper Networks Junos OS 21.3R3-S1, 21.4R3, 22.1R2 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
A Deadlock vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When a large amount of traffic is processed by ATP Cloud inspection, a deadlock can occur which will result in a PFE crash and restart. Whether the crash occurs, depends on system internal timing that is outside the attackers control. This issue affects Junos OS on SRX Series: * All versions before 21.3R3-S1, * 21.4 versions before 21.4R3, * 22.1 versions before 22.1R2, * 22.2 versions before 22.2R1-S2, 22.2R2.
- Published
- Oct 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-833
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:H/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.
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 | srx1500 | cpe:2.3:h:juniper:srx1500 |
| juniper | srx1600 | cpe:2.3:h:juniper:srx1600 |
| juniper | srx2300 | cpe:2.3:h:juniper:srx2300 |
| juniper | srx300 | cpe:2.3:h:juniper:srx300 |
| juniper | srx320 | cpe:2.3:h:juniper:srx320 |
| juniper | srx340 | cpe:2.3:h:juniper:srx340 |
| juniper | srx345 | cpe:2.3:h:juniper:srx345 |
| juniper | srx380 | cpe:2.3:h:juniper:srx380 |
| juniper | srx4100 | cpe:2.3:h:juniper:srx4100 |
| juniper | srx4120 | cpe:2.3:h:juniper:srx4120 |
| juniper | srx4200 | cpe:2.3:h:juniper:srx4200 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 21.3
- juniper junos21.3
- juniper junos21.4
- juniper junos22.1
- juniper junos22.2
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
- before 21.3R3-S1affected · semver
- 21.4 and later · before 21.4R3affected · semver
- 22.1 and later · before 22.1R2affected · semver
- 22.2 and later · before 22.2R1-S2, 22.2R2affected · 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-47503Oct 11, 2024 · Junos OS: SRX4600 and SRX5000 Series: Sequence of specific PIM packets causes a flowd crash28Monitor
- ← EarlierCVE-2024-47504Oct 11, 2024 · Junos OS: SRX5000 Series: Receipt of a specific malformed packet will cause a flowd crash34Monitor
- Later →CVE-2024-47507Oct 11, 2024 · Junos OS and Junos OS Evolved: BGP update message containing aggregator attribute with an ASN value of zero (0) is accepted27Monitor
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.3R3-S1 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.4R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.1R2 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R1-S2, 22.2R2 | 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.
No nightly-computed relations.
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1673 · Oct 14, 2024(Juniper Junos OS Güvenlik Bildirimi)
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
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-833 · DeadlockCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/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:M/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.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.