CVE-2025-52981: Junos OS: SRX Series: Sequence of specific PIM packets causes a flowd 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.51% (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.2R3-S9, 21.4R3-S11, 22.2R3-S7.
Low priority for now. Upgrade to Juniper Networks Junos OS 21.2R3-S9, 21.4R3-S11, 22.2R3-S7 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 Check for Unusual or Exceptional Conditions vulnerability in the flow processing daemon (flowd) of Juniper Networks Junos OS on SRX1600, SRX2300, SRX 4000 Series, and SRX5000 Series with SPC3 allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). If a sequence of specific PIM packets is received, this will cause a flowd crash and restart. This issue affects Junos OS: * all versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S11, * 22.2 versions before 22.2R3-S7, * 22.4 versions before 22.4R3-S6, * 23.2 versions before 23.2R2-S4, * 23.4 versions before 23.4R2-S4, * 24.2 versions before 24.2R2. This is a similar, but different vulnerability than the issue reported as CVE-2024-47503, published in JSA88133.
- Published
- Jul 11, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-754
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.5%
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 | srx1600 | cpe:2.3:h:juniper:srx1600 |
| juniper | srx2300 | cpe:2.3:h:juniper:srx2300 |
| juniper | srx4100 | cpe:2.3:h:juniper:srx4100 |
| juniper | srx4120 | cpe:2.3:h:juniper:srx4120 |
| juniper | srx4200 | cpe:2.3:h:juniper:srx4200 |
| juniper | srx4300 | cpe:2.3:h:juniper:srx4300 |
| juniper | srx4600 | cpe:2.3:h:juniper:srx4600 |
| juniper | srx4700 | cpe:2.3:h:juniper:srx4700 |
| juniper | srx5400 | cpe:2.3:h:juniper:srx5400 |
| juniper | srx5600 | cpe:2.3:h:juniper:srx5600 |
| juniper | srx5800 | cpe:2.3:h:juniper:srx5800 |
and 1 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.2R3-S9affected · semver
- 21.4 and later · before 21.4R3-S11affected · semver
- 22.2 and later · before 22.2R3-S7affected · semver
- 22.4 and later · before 22.4R3-S6affected · semver
- 23.2 and later · before 23.2R2-S4affected · semver
- 23.4 and later · before 23.4R2-S4affected · semver
- 24.2 and later · before 24.2R2affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- juniper junosbefore 21.2
- juniper junos21.2
- juniper junos21.4
- juniper junos22.2
- juniper junos22.4
- juniper junos23.2
- juniper junos23.4
- juniper junos24.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-2025-52964Jul 11, 2025 · Junos OS and Junos OS Evolved: Receipt of a specific BGP UPDATE causes an rpd crash on devices with BGP multipath configured28Monitor
- ← EarlierCVE-2025-52980Jul 11, 2025 · Junos OS: SRX300 Series: rpd will crash upon receiving a specific, valid BGP UPDATE message34Monitor
- Later →CVE-2025-52982Jul 11, 2025 · Junos OS: MX Series: When specific SIP packets are processed the MS-MPC will crash32Monitor
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.2R3-S9 | Vendor (CNA) |
| Juniper Networks Junos OS | 21.4R3-S11 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.2R3-S7 | Vendor (CNA) |
| Juniper Networks Junos OS | 22.4R3-S6 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.2R2-S4 | Vendor (CNA) |
| Juniper Networks Junos OS | 23.4R2-S4 | Vendor (CNA) |
| Juniper Networks Junos OS | 24.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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-6000490 days apartJunos OS and Junos OS Evolved: Specific BGP EVPN update message causes rpd crash34Monitor
- CVE-2025-2159493 days apartJunos OS: MX Series: In DS-lite and NAT scenario receipt of crafted IPv6 traffic causes port block34Monitor
- CVE-2025-3066093 days apartJunos OS: MX Series: Decapsulation of specific GRE packets leads to PFE reset34Monitor
- CVE-2026-33790272 days apartJunos OS: SRX Series: In a NAT64 configuration, receipt of a specific, malformed ICMPv6 packet will cause the srxpfe process to crash and restart.34Monitor
- CVE-2024-47499273 days apartJunos OS and Junos OS Evolved: In a BMP scenario receipt of a malformed AS PATH attribute can cause an RPD crash34Monitor
- CVE-2024-39530365 days apartJunos OS: Attempting to access specific sensors on platforms not supporting these will lead to a chassisd crash34Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · 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-754 · Improper Check for Unusual or Exceptional ConditionsCVSS 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:Y/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.
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.