dbcve.org
JunosOperating system · Juniper

CVE-2022-22246

HIGH · 8.8 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to 19.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 PHP Local File Inclusion (LFI) vulnerability in the J-Web component of Juniper Networks Junos OS may allow a low-privileged authenticated attacker to execute an untrusted PHP file. By chaining this vulnerability with other unspecified vulnerabilities, and by circumventing existing attack requirements, successful exploitation could lead to a complete system compromise. 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-S6; 19.4 versions prior to 19.4R2-S7, 19.4R3-S8; 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-S2; 21.2 versions prior to 21.2R3-S1; 21.3 versions prior to 21.3R2-S2, 21.3R3; 21.4 versions prior to 21.4R1-S2, 21.4R2-S1, 21.4R3; 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

PHP Local File Inclusion (LFI) vulnerability in the J-Web component of Juniper Networks Junos OS allows a low-privileged authenticated attacker to execute untrusted PHP files. Successful exploitation, especially when chained with other vulnerabilities, can lead to complete system compromise.

MitigationUpgrade Junos OS to a patched version as specified in the Juniper advisory. If immediate upgrade is not feasible, disable or restrict access to the J-Web component.

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

CVSS:3.1/AV:N/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. Verify J-Web component is accessible
    Check if the J-Web interface is enabled and reachable on the device. This is typically accessed via HTTP/HTTPS on port 8080 or 8443. Attempt to access the J-Web login page or check device configuration for 'system services web-management' settings.
    Affected if J-Web is enabled and exposed to the network, especially without strict access controls
  2. Confirm Junos OS version
    Run the command 'show version' or 'show version detail' on the device CLI to obtain the exact Junos OS version installed.
    Affected if The installed version matches any of these: 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, 21.2, 21.3, or any version earlier than 19.1
  3. Verify low-privilege access to J-Web
    Check if any user accounts with limited privileges (non-root/administrator) have access to the J-Web component. Review user authentication and authorization settings related to J-Web access.
    Affected if Low-privileged authenticated users can access the J-Web interface

The system is affected if J-Web is enabled and the Junos OS version is 19.1 through 21.3 (inclusive) or any version below 19.1, especially when low-privileged users have J-Web access.

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

Upgrade Junos OS to a patched version as specified in the Juniper advisory. If immediate upgrade is not feasible, disable or restrict access to the J-Web component.

Recommended fix High confidence

19.1R3-S9, 19.2R3-S6, or 19.3R3-S6 (or later stable releases)

  1. 1. Identify the current Junos OS version installed on the affected device using 'show version' command
  2. 2. Determine the appropriate upgrade path based on the current version and the fixed releases listed
  3. 3. Download the appropriate Junos SR (Service Release) or S9+ patch from the Juniper Networks download portal (https://www.juniper.net/customers/csc/software/)
  4. 4. Transfer the upgrade package to the device using SCP or USB storage
  5. 5. Install the 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' and confirm it matches a fixed release (19.1R3-S9 or later, 19.2R3-S6 or later, 19.3R3-S6 or later)
Caveat Standard Junos upgrade considerations apply - review release notes for any changes to features, syntax, or migration requirements before upgrading

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

Fix this in Junos Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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