CVE-2022-22246

Junos OS: PHP file inclusion vulnerability in J-Web

HIGH

8.8

CVSS Score

Published: October 18, 2022 at 02:46 AM UTC

Updated: June 17, 2026 at 04:28 AM UTC

1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.8

Exploit prediction

EPSS 0.8%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos · Juniper Networks

95%

v < 19.1v < 19.1R3-S919.2 ≤ v < 19.2R3-S619.3 ≤ v < 19.3R3-S619.4 ≤ v < 19.4R2-S7, 19.4R3-S820.1 ≤ v < 20.1R3-S520.2 ≤ v < 20.2R3-S520.3 ≤ v < 20.3R3-S520.4 ≤ v < 20.4R3-S421.1 ≤ v < 21.1R3-S221.2 ≤ v < 21.2R3-S121.3 ≤ v < 21.3R2-S2, 21.3R321.4 ≤ v < 21.4R1-S2, 21.4R2-S1, 21.4R322.1 ≤ v < 22.1R1-S1, 22.1R219.1 19.1 r1 19.1 r1-s1 19.1 r1-s2 19.1 r1-s3 19.1 r1-s4 19.1 r1-s5 19.1 r1-s6 19.1 r2 19.1 r2-s1 19.1 r2-s2 19.1 r2-s3 19.1 r3 19.1 r3-s1 19.1 r3-s2 19.1 r3-s3 19.1 r3-s4 19.1 r3-s5 19.1 r3-s6 19.1 r3-s7 19.1 r3-s8 19.2 19.2 r1 19.2 r1-s1 19.2 r1-s2 19.2 r1-s3 19.2 r1-s4 19.2 r1-s5 19.2 r1-s6 19.2 r1-s7 19.2 r1-s8 19.2 r1-s9 19.2 r2 19.2 r2-s1 19.2 r3 19.2 r3-s1 19.2 r3-s2 19.2 r3-s3 19.2 r3-s4 19.2 r3-s5 19.3 19.3 r1 19.3 r1-s1 19.3 r2 19.3 r2-s1 19.3 r2-s2 19.3 r2-s3 19.3 r2-s4 19.3 r2-s5 19.3 r2-s6 19.3 r3 19.3 r3-s1 19.3 r3-s2 19.3 r3-s3 19.3 r3-s4 19.3 r3-s5 19.3 r3-s6 19.4 19.4 r1 19.4 r1-s1 19.4 r1-s2 19.4 r1-s3 19.4 r1-s4 19.4 r2 19.4 r2-s1 19.4 r2-s2 19.4 r2-s3 19.4 r2-s4 19.4 r2-s5 19.4 r2-s6 19.4 r3 19.4 r3-s1 19.4 r3-s2 19.4 r3-s3 19.4 r3-s4 19.4 r3-s5 19.4 r3-s6 19.4 r3-s7 19.4 r3-s8 20.1 20.1 r1 20.1 r1-s1 20.1 r1-s2 20.1 r1-s3 20.1 r1-s4 20.1 r2 20.1 r2-s1 20.1 r2-s2 20.1 r3 20.1 r3-s1 20.1 r3-s2 20.1 r3-s3 20.1 r3-s4 20.2 20.2 r1 20.2 r1-s1 20.2 r1-s2 20.2 r1-s3 20.2 r2 20.2 r2-s1 20.2 r2-s2 20.2 r2-s3 20.2 r3 20.2 r3-s1 20.2 r3-s2 20.2 r3-s3 20.2 r3-s4 20.3 20.3 r1 20.3 r1-s1 20.3 r1-s2 20.3 r2 20.3 r2-s1 20.3 r3 20.3 r3-s1 20.3 r3-s2 20.3 r3-s3 20.4 20.4 r1 20.4 r1-s1 20.4 r2 20.4 r2-s1 20.4 r2-s2 20.4 r3 20.4 r3-s1 20.4 r3-s2 20.4 r3-s3 21.1 21.1 r1 21.1 r1-s1 21.1 r2 21.1 r2-s1 21.1 r2-s2 21.1 r3 21.1 r3-s1 21.2 21.2 r1 21.2 r1-s1 21.2 r1-s2 21.2 r2 21.2 r2-s1 21.2 r2-s2 21.2 r3 21.3 21.3 r1 21.3 r1-s1 21.3 r1-s2 21.3 r2 21.3 r2-s1 21.3 r2-s2 21.4 21.4 r1 21.4 r1-s1 21.4 r1-s2 21.4 r2 21.4 r2-s1 21.4 r2-s2 22.1 22.1 r1 22.1 r1-s1 22.1 r1-s2

Affected range stops below 19.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.1R3-S9, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.2R3-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.3R3-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.4R2-S7, 19.4R3-S8, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.1R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.2R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.3R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.4R3-S4, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.1R3-S2, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.2R3-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.3R2-S2, 21.3R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.4R1-S2, 21.4R2-S1, 21.4R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.1R1-S1, 22.1R2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://kb.juniper.net/JSA69899

References (1)

Vendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA69899

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGH[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-829

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card