dbcve.org
JunosOperating system · Juniper

CVE-2022-22181

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-14
Fix available
A fix is available. Upgrade to 18.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 reflected Cross-site Scripting (XSS) vulnerability in J-Web of Juniper Networks Junos OS allows a network-based authenticated attacker to run malicious scripts reflected off J-Web to the victim's browser in the context of their session within J-Web. This may allow the attacker to gain control of the device or attack other authenticated user sessions. This issue affects: Juniper Networks Junos OS All versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R3-S9; 19.1 versions prior to 19.1R3-S6; 19.2 versions prior to 19.2R3-S3; 19.3 versions prior to 19.3R2-S6, 19.3R3-S3; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R3-S4; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R1-S1, 21.1R2.

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 reflected Cross-site Scripting (XSS) vulnerability in the J-Web interface of Juniper Networks Junos OS allows an authenticated network-based attacker to inject malicious scripts that are reflected back to victim browsers within their J-Web session context, potentially enabling session hijack or further attacks on the device.

MitigationApply the vendor-supplied Junos OS patches for the specific version running (see CVE-affected version list), or upgrade to a patched release.

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:< 18.3= 18.3= 18.4= 19.1= 19.2= 19.3= 19.4= 20.1= 20.2= 20.3= 20.4= 21.1

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check Junos OS version
    Run `show version` or `show version invoke-on all-routing-engines` on the device CLI to retrieve the installed Junos OS version.
    Affected if The version shown is any of: 18.3, 18.4, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, or any version prior to 18.3.
  2. Verify J-Web interface is enabled
    Run `show system services web-management` to check if web-based management (J-Web) is enabled on the device.
    Affected if The output shows web-management http or https service is enabled (any http or https configuration is present).
  3. Confirm J-Web is accessible over the network
    Review the web-management configuration with `show configuration system services web-management` to determine if J-Web is bound to a reachable interface (e.g., ge-0/0/0, fxp0, or any IP-assigned interface).
    Affected if The J-Web service is bound to a network-accessible interface rather than loopback-only or completely disabled.

The device is affected if it runs a vulnerable Junos OS version (18.3 through 21.1 or any version below 18.3) AND has J-Web interface enabled and accessible on the network.

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

Apply the vendor-supplied Junos OS patches for the specific version running (see CVE-affected version list), or upgrade to a patched release.

Recommended fix High confidence

Upgrade to the first fixed version in your release branch: 18.3R3-S5, 18.4R3-S9, 19.1R3-S6, 19.2R3-S3, 19.3R3-S3, 19.4R3-S5, 20.1R3-S4, 20.2R3-S2, 20.3R3, 20.4R3, or 21.1R2 (or later)

  1. 1. Identify the current Junos OS version on the device using 'show version' command
  2. 2. Review Juniper Knowledge Base article kb.juniper.net for this CVE for any additional patch or configuration guidance
  3. 3. Back up the current device configuration using 'request system configuration rescue save'
  4. 4. Plan maintenance window as J-Web upgrade may cause brief service disruption
  5. 5. Download the appropriate fixed Junos release from Juniper Networks based on your current version branch
  6. 6. Upgrade the device using 'request system software add <package-name>' or via J-Web/CLI
  7. 7. After reboot, verify the new version is installed using 'show version'
  8. 8. Confirm the J-Web XSS vulnerability is resolved by attempting to reproduce the XSS condition or by verifying the installed version includes the fix
Caveat Review Juniper release notes for your specific upgrade path for any compatibility warnings or configuration changes required between major versions

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
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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