dbcve.org
JunosOperating system · Juniper

CVE-2022-22244

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 19.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 XPath Injection vulnerability in the J-Web component of Juniper Networks Junos OS allows an unauthenticated attacker sending a crafted POST to reach the XPath channel, which may allow chaining to other unspecified vulnerabilities, leading to a partial loss of confidentiality. This issue affects Juniper Networks Junos OS: all versions prior to 19.1R3-S9; 19.2 versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S7; 19.4 versions prior to 19.4R3-S9; 20.1 versions prior to 20.1R3-S5; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S5; 20.4 versions prior to 20.4R3-S4; 21.1 versions prior to 21.1R3-S3; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R3; 21.4 versions prior to 21.4R1-S2, 21.4R2; 22.1 versions prior to 22.1R1-S1, 22.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

An XPath Injection vulnerability exists in the J-Web component of Juniper Networks Junos OS. An unauthenticated attacker can send crafted POST requests to reach the XPath channel, potentially chaining to other unspecified vulnerabilities. This may result in partial loss of confidentiality.

MitigationApply the vendor-supplied patches for affected Junos OS versions or disable the J-Web component if not required, and restrict access to management interfaces.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify Junos OS version
    Run 'show version' or 'show system information' on the device CLI to obtain the installed Junos OS version number.
    Affected if The installed version matches any of these: < 19.1, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, or 21.3.
  2. Confirm J-Web component is enabled
    Run 'show configuration system services web-management' to check if J-Web is configured and active.
    Affected if J-Web is enabled and operational on the device.
  3. Verify J-Web access settings
    Review the web-management configuration for http or http-enabled settings and interface bindings. Check if J-Web is bound to external-facing interfaces.
    Affected if J-Web is accessible from untrusted networks or management interfaces are not restricted.
  4. Check for suspicious POST request logs
    Review system logs (show log messages) for unusual POST requests to J-Web endpoints, particularly those containing XPath-related patterns or injection attempts.
    Affected if Logs show unexpected POST requests to J-Web from untrusted sources.

The environment is affected if the device runs a vulnerable Junos OS version (19.1 through 21.3) AND has J-Web component enabled and reachable, particularly from untrusted networks.

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

Apply the vendor-supplied patches for affected Junos OS versions or disable the J-Web component if not required, and restrict access to management interfaces.

Recommended fix High confidence

19.1R3-S9, 19.2R3-S6, 19.3R3-S7, or later releases within each version 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, identify the minimum fixed release: for 19.1.x upgrade to 19.1R3-S9; for 19.2.x upgrade to 19.2R3-S6; for 19.3.x upgrade to 19.3R3-S7; for 19.4.x upgrade to 19.4R3-S9; for 20.1.x upgrade to 20.1R3-S5; for 20.2.x upgrade to 20.2R3-S5; for 20.3.x upgrade to 20.3R3-S5; for 20.4.x upgrade to 20.4R3-S4; for 21.1.x upgrade to 21.1R3-S3; for 21.2.x upgrade to 21.2R
  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 FTP/SCP to /var/tmp/
  5. 5. Initiate the upgrade using 'request system software add <package>' command
  6. 6. After installation completes, reboot the device using 'request system reboot'
  7. 7. Verify the new version is installed using 'show version' and confirm the fix is applied
Caveat Standard Junos upgrade precautions apply - verify compatibility with existing configurations and review Juniper upgrade documentation

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-22244 — 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-22244 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