dbcve.org
JunosOperating system · Juniper

CVE-2025-30652

MEDIUM · 5.5 CVSS v3.1 Published 2025-04-09
Fix available
A fix is available. Upgrade to 21.2 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Improper Handling of Exceptional Conditions vulnerability in routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privileged attacker executing a CLI command to cause a Denial of Service (DoS). When asregex-optimized is configured and a specific "show route as-path" CLI command is executed, the rpd crashes and restarts. Repeated execution of this command will cause a sustained DoS condition. This issue affects Junos OS: * All versions before 21.2R3-S9, * from 21.4 before 21.4R3-S10, * from 22.2 before 22.2R3-S6, * from 22.4 before 22.4R3-S6, * from 23.2 before 23.2R2-S3, * from 23.4 before 23.4R2-S4, * from 24.2 before 24.2R2. and Junos OS Evolved: * All versions before 21.2R3-S9-EVO, * from 21.4-EVO before 21.4R3-S10-EVO, * from 22.2-EVO before 22.2R3-S6-EVO, * from 22.4-EVO before 22.4R3-S6-EVO, * from 23.2-EVO before 23.2R2-S3-EVO, * from 23.4-EVO before 23.4R2-S4-EVO, * from 24.2-EVO before 24.2R2-EVO.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A local low-privileged attacker with CLI access can trigger a crash of the routing protocol daemon (rpd) in Juniper Junos OS/Evolved by executing a specific 'show route as-path' command when the 'asregex-optimized' feature is configured. The rpd crashes and restarts, and repeated execution causes a sustained DoS condition.

MitigationApply the appropriate Junos OS or Junos OS Evolved patch version as specified in the vendor advisory (versions listed for each branch). As a temporary mitigation, avoid using the 'asregex-optimized' configuration if possible, and limit CLI access to trusted personnel.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 21.2= 21.2= 21.4= 22.2= 22.4= 23.2= 23.4= 24.2
Junos Os EvolvedOperating system
Affected:< 21.2= 21.2= 21.4= 22.2= 22.4= 23.2= 23.4= 24.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Junos OS/Evolved version
    Execute 'show version' in the CLI to obtain the installed software version
    Affected if Version matches < 21.2, = 21.2, = 21.4, = 22.2, = 22.4, = 23.2, = 23.4, or = 24.2 for either Junos or Junos Evolved
  2. Verify asregex-optimized configuration
    Execute 'show configuration | match asregex-optimized' in operational mode CLI
    Affected if The command returns configuration output, indicating asregex-optimized is enabled under the routing options
  3. Inspect rpd crash history
    Execute 'show log messages | match rpd' or 'show system core-dumps' to review recent routing daemon crashes
    Affected if Recent rpd crash events are logged, especially if triggered by 'show route as-path' commands

A device is affected if it runs a vulnerable Junos/Evolved version AND has the asregex-optimized feature configured, with potential evidence of rpd crashes from the show route as-path command.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 21.2 or later
Fixed in 21.2
Interim mitigation

Apply the appropriate Junos OS or Junos OS Evolved patch version as specified in the vendor advisory (versions listed for each branch). As a temporary mitigation, avoid using the 'asregex-optimized' configuration if possible, and limit CLI access to trusted personnel.

Recommended fix High confidence

21.2R3-S9 or later (21.2 branch), 21.4R3-S10 or later (21.4 branch), 22.2R3-S6 or later (22.2 branch), 22.4R3-S6 or later (22.4 branch), 23.2R2-S3 or later (23.2 branch), 23.4R2-S4 or later (23.4 branch), 24.2R2 or later (24.2 branch) - select based on current branch

  1. 1. Identify the currently installed Junos OS or Junos OS Evolved version using 'show version'
  2. 2. Identify if 'asregex-optimized' is configured in the current configuration using 'show configuration | match asregex-optimized'
  3. 3. Plan an upgrade to a fixed version based on the current branch: For 21.2.x upgrade to 21.2R3-S9 or later; For 21.4.x upgrade to 21.4R3-S10 or later; For 22.2.x upgrade to 22.2R3-S6 or later; For 22.4.x upgrade to 22.4R3-S6 or later; For 23.2.x upgrade to 23.2R2-S3 or later; For 23.4.x upgrade to 23.4R2-S4 or later; For 24.2.x upgrade to 24.2R2 or later
  4. 4. Before upgrading, verify the target version compatibility with your hardware platform using Juniper's release notes
  5. 5. Schedule a maintenance window as the upgrade will require a system reboot
  6. 6. Back up the current configuration using 'request system configuration rescue save'
  7. 7. Perform the upgrade using 'request system software add <package-name>' for Junos OS or the appropriate method for Junos OS Evolved
  8. 8. After upgrade, verify the fix by confirming the version and ensuring rpd is stable
Caveat Standard Junos upgrade considerations apply - review release notes for any configuration changes, new features, or deprecated functionality before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30652 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data