dbcve.org
JunosOperating system · Juniper

CVE-2022-22162

HIGH · 7.8 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to 15.1 or later.
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
A Generation of Error Message Containing Sensitive Information vulnerability in the CLI of Juniper Networks Junos OS allows a locally authenticated attacker with low privileges to elevate these to the level of any other user logged in via J-Web at this time, potential leading to a full compromise of the device. This issue affects Juniper Networks Junos OS: All versions prior to 15.1R7-S11; 18.3 versions prior to 18.3R3-S6; 18.4 versions prior to 18.4R2-S9, 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R3-S6; 20.1 versions prior to 20.1R3-S2; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3-S1; 21.1 versions prior to 21.1R2-S1, 21.1R3; 21.2 versions prior to 21.2R1-S1, 21.2R2.

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 locally authenticated low-privilege attacker can exploit the Junos OS CLI to elevate privileges to any other user currently logged into J-Web, potentially achieving full device compromise. The vulnerability stems from sensitive information disclosure in error messages that can be leveraged to hijack active sessions.

MitigationUpgrade Junos OS to a patched version as specified in the version list (e.g., 15.1R7-S11, 18.3R3-S6, 18.4R3-S10, or later versions in each branch).

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:< 15.1= 15.1= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.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 Junos OS version
    Execute 'show version' or 'show version detail' in the CLI. Locate the Junos OS version string (typically displayed as something like 15.1R1, 18.4R3, etc.)
    Affected if The installed version matches one of the affected versions listed: any version < 15.1, or exactly 15.1, 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, or 20.4
  2. Verify J-Web is enabled
    Execute 'show configuration system services web-management' to see if J-Web (HTTP or HTTPS) is configured and active
    Affected if J-Web web-management service is enabled and accessible (the vulnerability exploits J-Web session hijacking, so J-Web must be running)
  3. Check for concurrent user sessions
    Execute 'show system users' or 'show system sessions' to list currently logged-in users and active sessions
    Affected if Multiple users are logged in simultaneously (the privilege escalation hijacks other active J-Web sessions)
  4. Confirm low-privilege CLI access exists
    Verify that low-privilege accounts can access the CLI (the attacker needs local CLI authentication)
    Affected if Non-administrator accounts have CLI login capability (the vulnerability requires authenticated local CLI access)

You are affected if your Junos OS version matches an affected version listed AND J-Web is enabled with multiple concurrent user sessions possible.

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 15.1 or later
Fixed in 15.1
Interim mitigation

Upgrade Junos OS to a patched version as specified in the version list (e.g., 15.1R7-S11, 18.3R3-S6, 18.4R3-S10, or later versions in each branch).

Recommended fix High confidence

15.1R7-S11, 18.3R3-S6, 18.4R2-S9/18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S6, 20.1R3-S2, 20.2R3-S3, 20.3R3-S1, 20.4R3-S1, 21.1R3, or 21.2R2 (depending on starting branch)

  1. 1. Identify the current Junos OS version running on the device using 'show version' command
  2. 2. Based on the current version branch, upgrade to the minimum fixed version: For 15.1 branch: upgrade to 15.1R7-S11 or later; For 18.3 branch: upgrade to 18.3R3-S6 or later; For 18.4 branch: upgrade to 18.4R2-S9 or later (or 18.4R3-S10 for additional fixes); For 19.1 branch: upgrade to 19.1R3-S7 or later; For 19.2 branch: upgrade to 19.2R3-S4 or later; For 19.3 branch: upgrade to 19.3R3-S4 or lat
  3. 3. Download the appropriate Junos software upgrade package from the Juniper Networks support portal
  4. 4. Transfer the upgrade package to the device using SCP or FTP
  5. 5. Initiate the software upgrade using 'request system software add <package-name>' command
  6. 6. Reboot the device using 'request system reboot' command to complete the installation
  7. 7. After reboot, verify the new version is installed using 'show version'
  8. 8. Verify the fix is applied by checking that low-privileged users can no longer access other users' J-Web sessions through error message leakage
Caveat Upgrading Junos OS may cause temporary service disruption during reboot; ensure proper change management and maintenance window is scheduled; some configuration compatibility checks should be performed before upgrade

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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