dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2025-60006

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/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
Multiple instances of an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in the CLI of Juniper Networks Junos OS Evolved could be used to elevate privileges and/or execute unauthorized commands. When an attacker executes crafted CLI commands, the options are processed via a script in some cases. These scripts are not hardened so injected commands might be executed via the shell, which allows an attacker to perform operations, which they should not be able to do according to their assigned permissions. This issue affects Junos OS Evolved: * 24.2 versions before 24.2R2-S2-EVO, * 24.4 versions before 24.4R2-EVO. This issue does not affect Junos OS Evolved versions earlier than 24.2R1-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

OS command injection vulnerability in Juniper Junos OS Evolved CLI where scripts processing CLI command options fail to properly sanitize special elements, allowing authenticated attackers to inject and execute arbitrary OS commands with elevated privileges beyond their assigned permissions.

MitigationApply vendor-supplied patches by upgrading to 24.2R2-S2-EVO, 24.4R2-EVO, or later versions; until patched, minimize attack surface by restricting CLI access to trusted personnel only.

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
Junos Os EvolvedOperating system
Affected:= 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
Low
Integrity
Low
Availability
Low

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

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. Confirm Junos OS Evolved is installed
    Run the command 'show version' or 'show version detail' in the CLI and examine the output for 'Junos OS Evolved' versus 'Junos OS' - this vulnerability only affects the Evolved variant
    Affected if The product is Junos OS Evolved (not regular Junos OS)
  2. Identify the installed version
    Run 'show version' and locate the version number in the output (for example: 24.2R1, 24.2R2, 24.4R1, etc.)
    Affected if The version is exactly 24.2 or 24.4 (including any subversions like 24.2R1, 24.4R1, etc.)
  3. Verify CLI access is available
    Confirm the CLI is accessible by logging in or checking system configuration for CLI access settings
    Affected if CLI is accessible to authenticated users (the vulnerability is exploited through CLI command options)
  4. Check for unauthorized CLI access accounts
    Run 'show system users' or review 'system login' configuration to identify all accounts with CLI access permissions
    Affected if There are any authenticated CLI users beyond trusted personnel (the vulnerability allows privilege escalation beyond assigned permissions)

The environment is affected if running Junos OS Evolved version 24.2 or 24.4 and the CLI is accessible to authenticated users, as the vulnerability allows command injection through CLI options.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches by upgrading to 24.2R2-S2-EVO, 24.4R2-EVO, or later versions; until patched, minimize attack surface by restricting CLI access to trusted personnel only.

Recommended fix High confidence

24.2R2-S2-EVO (for 24.2 branch) or 24.4R2-EVO (for 24.4 branch)

  1. 1. Identify the current Junos OS Evolved version using 'show version' command
  2. 2. If running 24.2.x, plan upgrade to 24.2R2-S2-EVO or later
  3. 3. If running 24.4.x, plan upgrade to 24.4R2-EVO or later
  4. 4. Schedule maintenance window for upgrade procedure
  5. 5. Backup current configuration using 'request system configuration rescue save'
  6. 6. Download the appropriate fixed Junos OS Evolved image from Juniper Networks support portal
  7. 7. Install the upgrade via 'request system software add <package> reboot'
  8. 8. After reboot, verify new version with 'show version' and confirm it meets the fixed version requirements
Caveat Standard Junos OS Evolved upgrade risks apply - ensure configuration compatibility and plan for brief downtime during reboot

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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