CVE-2021-0269

Junos OS: J-Web can be compromised through reflected client-side HTTP parameter pollution attacks.

HIGH

8.8

CVSS Score

Published: April 22, 2021 at 07:37 PM UTC

Updated: June 17, 2026 at 03:29 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.9%

Description

The improper handling of client-side parameters in J-Web of Juniper Networks Junos OS allows an attacker to perform a number of different malicious actions against a target device when a user is authenticated to J-Web. An attacker may be able to supersede existing parameters, including hardcoded parameters within the HTTP/S session, access and exploit variables, bypass web application firewall rules or input validation mechanisms, and otherwise alter and modify J-Web's normal behavior. An attacker may be able to transition victims to malicious web services, or exfiltrate sensitive information from otherwise secure web forms. This issue affects: Juniper Networks Junos OS: All versions prior to 17.4R3-S3; 18.1 versions prior to 18.1R3-S12; 18.2 versions prior to 18.2R3-S6; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R2-S2, 19.4R3; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2.

Affected

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

Junos · Juniper Networks

95%

v < 17.4R3-S318.1 ≤ v < 18.1R3-S1218.2 ≤ v < 18.2R3-S618.3 ≤ v < 18.3R3-S418.4 ≤ v < 18.4R3-S619.1 ≤ v < 19.1R3-S419.2 ≤ v < 19.2R3-S119.3 ≤ v < 19.3R3-S119.4 ≤ v < 19.4R2-S2, 19.4R320.1 ≤ v < 20.1R220.2 ≤ v < 20.2R217.4 17.4 r1 17.4 r1-s1 17.4 r1-s2 17.4 r1-s3 17.4 r1-s4 17.4 r1-s5 17.4 r1-s6 17.4 r1-s7 17.4 r2 17.4 r2-s1 17.4 r2-s10 17.4 r2-s11 17.4 r2-s2 17.4 r2-s3 17.4 r2-s4 17.4 r2-s5 17.4 r2-s6 17.4 r2-s7 17.4 r2-s8 17.4 r2-s9 17.4 r3 17.4 r3-s1 17.4 r3-s2 18.1 18.1 r1 18.1 r2 18.1 r2-s1 18.1 r2-s2 18.1 r2-s4 18.1 r3 18.1 r3-s1 18.1 r3-s10 18.1 r3-s11 18.1 r3-s2 18.1 r3-s3 18.1 r3-s4 18.1 r3-s5 18.1 r3-s6 18.1 r3-s7 18.1 r3-s8 18.1 r3-s9 18.2 18.2 r1 18.2 r1-s2 18.2 r1-s3 18.2 r1-s4 18.2 r1-s5 18.2 r2 18.2 r2-s1 18.2 r2-s2 18.2 r2-s3 18.2 r2-s4 18.2 r2-s5 18.2 r2-s6 18.2 r2-s7 18.2 r3 18.2 r3-s1 18.2 r3-s2 18.2 r3-s3 18.2 r3-s4 18.2 r3-s5 18.3 18.3 r1 18.3 r1-s1 18.3 r1-s2 18.3 r1-s3 18.3 r1-s4 18.3 r1-s5 18.3 r1-s6 18.3 r2 18.3 r2-s1 18.3 r2-s2 18.3 r2-s3 18.3 r2-s4 18.3 r3 18.3 r3-s1 18.3 r3-s2 18.3 r3-s3 18.4 18.4 r1 18.4 r1-s1 18.4 r1-s2 18.4 r1-s3 18.4 r1-s4 18.4 r1-s5 18.4 r1-s6 18.4 r1-s7 18.4 r2 18.4 r2-s1 18.4 r2-s2 18.4 r2-s3 18.4 r2-s4 18.4 r2-s5 18.4 r2-s6 18.4 r3 18.4 r3-s1 18.4 r3-s2 18.4 r3-s3 18.4 r3-s4 18.4 r3-s5 19.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 r2 19.1 r2-s1 19.1 r3 19.1 r3-s1 19.1 r3-s2 19.1 r3-s3 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 r2 19.2 r2-s1 19.2 r3 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 r3 19.4 19.4 r1 19.4 r1-s1 19.4 r1-s2 19.4 r2 19.4 r2-s1 20.1 20.1 r1 20.1 r1-s1 20.1 r1-s2 20.1 r1-s3 20.1 r1-s4 20.2 20.2 r1 20.2 r1-s1 20.2 r1-s2 20.2 r1-s3

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

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

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

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

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

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

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

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

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

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

Affected range stops below 20.2R2, 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/JSA11160

References (1)

x_refsource_MISCVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11160

CVSS

8.8HIGHjuniper

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

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-233NVD-CWE-Other

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