CVE-2024-39529: Junos OS: SRX Series: If DNS traceoptions are configured in a DGA or tunnel detection scenario specific DNS traffic leads to a PFE crash
Noroxi assessment
Priority: Monitor (action score 34/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.47% (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-S6, 22.2R3-S3, 22.3R3-S3.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Juniper Networks Junos OS 21.4R3-S6, 22.2R3-S3, 22.3R3-S3 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 Use of Externally-Controlled Format String 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). If DNS Domain Generation Algorithm (DGA) detection or tunnel detection, and DNS-filtering traceoptions are configured, and specific valid transit DNS traffic is received this causes a PFE crash and restart, leading to a Denial of Service. This issue affects Junos OS: * All versions before 21.4R3-S6, * 22.2 versions before 22.2R3-S3, * 22.3 versions before 22.3R3-S3, * 22.4 versions before 22.4R3, * 23.2 versions before 23.2R2.
- Published
- Jul 11, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-134
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · juniper
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/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 | srx100 | cpe:2.3:h:juniper:srx100 |
| juniper | srx110 | cpe:2.3:h:juniper:srx110 |
| juniper | srx1400 | cpe:2.3:h:juniper:srx1400 |
| juniper | srx1500 | cpe:2.3:h:juniper:srx1500 |
| juniper | srx1600 | cpe:2.3:h:juniper:srx1600 |
| juniper | srx210 | cpe:2.3:h:juniper:srx210 |
| juniper | srx220 | cpe:2.3:h:juniper:srx220 |
| juniper | srx2300 | cpe:2.3:h:juniper:srx2300 |
| juniper | srx240 | cpe:2.3:h:juniper:srx240 |
| juniper | srx240h2 | cpe:2.3:h:juniper:srx240h2 |
| juniper | srx240m | cpe:2.3:h:juniper:srx240m |
and 21 more
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.4R3-S6affected · semver
- 22.2 and later · before 22.2R3-S3affected · semver
- 22.3 and later · before 22.3R3-S3affected · semver
- 22.4 and later · before 22.4R3affected · semver
- 23.2 and later · before 23.2R2affected · 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 junosbefore 21.4
- juniper junos21.4
- juniper junos22.2
- juniper junos22.3
- juniper junos22.4
- juniper junos23.2
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-39561Jul 10, 2024 · Junos OS: SRX4600, SRX5000 Series: TCP packets with SYN/FIN or SYN/RST are transferred after enabling no-syn-check with Express Path27Monitor
- ← EarlierCVE-2024-39528Jul 11, 2024 · Junos OS and Junos OS Evolved: Concurrent deletion of a routing-instance and receipt of an SNMP request cause an RPD crash24Monitor
- Later →CVE-2024-39530Jul 11, 2024 · Junos OS: Attempting to access specific sensors on platforms not supporting these will lead to a chassisd 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 | 21.4R3-S6 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.3R3-S3 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R3 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.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.
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 · variant or chain candidate · public bounty program.
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-134 · Use of Externally-Controlled Format StringCVSS vector
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: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.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.