dbcve.org
JunosOperating system · Juniper

CVE-2025-60007

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-15
Fix available
A fix is available. Upgrade to 22.4 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
A NULL Pointer Dereference vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS on MX, SRX and EX Series allows a local attacker with low privileges to cause a Denial-of-Service (DoS). When a user executes the 'show chassis' command with specifically crafted options, chassisd will crash and restart. Due to this all components but the Routing Engine (RE) in the chassis are reinitialized, which leads to a complete service outage, which the system automatically recovers from. This issue affects: Junos OS on MX, SRX and EX Series, except MX10000 Series and MX304:  * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5, * 23.4 versions before 23.4R2-S6, * 24.2 versions before 24.2R2-S2, * 24.4 versions before 24.4R2.

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 NULL pointer dereference vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS allows a local low-privileged attacker to crash chassisd by executing the 'show chassis' command with specifically crafted options, causing all non-RE chassis components to reinitialize and service outage until auto-recovery.

MitigationApply the appropriate Junos OS patch (22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, or 24.4R2 or later) per Juniper's revision matrix; until patched, consider restricting CLI access to untrusted users.

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:< 22.4= 22.4= 23.2= 23.4= 24.2= 24.4

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 installed Junos OS version
    Execute 'show version' or 'show version detail' in the CLI to retrieve the exact Junos OS version running on the device
    Affected if The displayed version is any of: < 22.4, 22.4 (any release), 23.2 (any release), 23.4 (any release), 24.2 (any release), or 24.4 (any release)
  2. Verify low-privileged user CLI access
    Review user account configurations and login class permissions using 'show system login' and check if untrusted or low-privilege users have CLI access
    Affected if Low-privileged or untrusted users have CLI access, as the attacker only needs local low-privileged access to execute the malicious 'show chassis' command
  3. Confirm 'show chassis' command availability
    Attempt to execute 'show chassis' via the CLI as a low-privileged user or review the command's permission requirements in the configuration
    Affected if The 'show chassis' command is accessible to low-privileged users, as this is the specific command with crafted options that triggers the NULL pointer dereference
  4. Review chassisd process stability
    Check system logs and crash logs for recent chassisd daemon restarts using 'show log messages' or 'request support information' to identify any unexpected chassisd crashes
    Affected if There are recent unexplained chassisd crashes or restarts, which would indicate the vulnerability may have been exploited

The environment is affected if the installed Junos OS version falls within 22.4, 23.2, 23.4, 24.2, 24.4 (any release within these branches) or any version below 22.4, AND low-privileged users have access to the 'show chassis' CLI 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 22.4 or later
Fixed in 22.4
Interim mitigation

Apply the appropriate Junos OS patch (22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, or 24.4R2 or later) per Juniper's revision matrix; until patched, consider restricting CLI access to untrusted users.

Recommended fix High confidence

22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S2, or 24.4R2 (depending on which branch you are on)

  1. Identify the current Junos OS version running on the MX, SRX, or EX Series device using 'show version'
  2. Determine which branch the current version belongs to (22.4, 23.2, 23.4, 24.2, or 24.4)
  3. Schedule a maintenance window for the upgrade (this will require a system reboot)
  4. Download the appropriate fixed version from Juniper Networks: For 22.4 branch: 22.4R3-S8 or later; For 23.2 branch: 23.2R2-S5 or later; For 23.4 branch: 23.4R2-S6 or later; For 24.2 branch: 24.2R2-S2 or later; For 24.4 branch: 24.4R2 or later
  5. Upload the Junos upgrade package to the device via FTP/SCP
  6. Install the upgrade using 'request system software add <package-name>' command
  7. Reboot the device using 'request system reboot' command
  8. After reboot, verify the new version is installed using 'show version'
Caveat Standard Junos upgrade - may require compatibility checking for specific MX, SRX, or EX Series hardware; ensure backup configuration is saved before upgrade

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60007 — 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-60007 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