dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2024-39522

HIGH · 7.8 CVSS v3.1 Published 2024-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Neutralization of Special Elements vulnerability in Juniper Networks Junos OS Evolved commands allows a local, authenticated attacker with low privileges to escalate their privileges to 'root' leading to a full compromise of the system. The Junos OS Evolved CLI doesn't properly handle command options in some cases, allowing users which execute specific CLI commands with a crafted set of parameters to escalate their privileges to root on shell level. This issue affects Junos OS Evolved: * 22.3-EVO versions before 22.3R2-EVO, * 22.4-EVO versions before 22.4R1-S1-EVO, 22.4R2-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

This is a local privilege escalation vulnerability in Juniper Junos OS Evolved where the CLI fails to properly sanitize special elements in command options. An authenticated low-privilege user can execute specific CLI commands with crafted parameters to gain root shell access, achieving full system compromise.

MitigationUpgrade Junos OS Evolved to version 22.3R2-EVO or later for 22.3-EVO branches, or 22.4R1-S1-EVO/22.4R2-EVO or later for 22.4-EVO branches to remediate this vulnerability.

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:= 22.3= 22.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the Junos OS variant
    Run 'show version' or 'show system information' and look for 'Junos OS Evolved' in the product name. This vulnerability only affects Junos OS Evolved, not standard Junos OS.
    Affected if The system is running Junos OS Evolved (not regular Junos OS)
  2. Check the exact Junos OS Evolved version
    Run 'show version' and locate the version string (for example: 22.3R1-S1-EVO, 22.4R1-EVO, etc.). Compare against the affected versions.
    Affected if The installed version is exactly 22.3 or 22.4 series (before 22.3R2-EVO or 22.4R2-EVO)
  3. Verify CLI access exists
    Confirm that low-privilege user accounts have CLI access. This is a prerequisite since the attack requires authenticated CLI command execution.
    Affected if Low-privilege users can access the CLI shell

A system is affected if it runs Junos OS Evolved version 22.3 or 22.4 (specifically pre-22.3R2-EVO or pre-22.4R2-EVO) and allows authenticated CLI access to low-privilege users.

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

Upgrade Junos OS Evolved to version 22.3R2-EVO or later for 22.3-EVO branches, or 22.4R1-S1-EVO/22.4R2-EVO or later for 22.4-EVO branches to remediate this vulnerability.

Recommended fix High confidence

22.3R2-EVO or later (for 22.3 branches); 22.4R1-S1-EVO or 22.4R2-EVO or later (for 22.4 branches)

  1. Identify the current Junos OS Evolved version using 'show version' command
  2. If running 22.3-EVO: upgrade to 22.3R2-EVO or later
  3. If running 22.4-EVO: upgrade to 22.4R1-S1-EVO or 22.4R2-EVO or later
  4. Schedule upgrade during a maintenance window
  5. After upgrade, verify the new version is installed using 'show version'
  6. Confirm the fix is applied by checking that low-privileged users can no longer escalate to root via CLI commands
Caveat Standard Junos OS Evolved upgrade considerations apply - test in lab environment first, review release notes for any compatibility notes, plan for potential downtime

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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