CVE-2020-1631: Juniper Junos OS Path Traversal
Juniper Junos OS · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-25.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 4.9%
- higher than 92.2% of all CVEs
- Added to CISA KEV
- 2022-03-25
- US federal due date 2022-04-15
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2020-1631 explained
CVE-2020-1631 is a path traversal and local file inclusion flaw in the HTTP/HTTPS service of Juniper Junos OS. This service is used by J-Web, Web Authentication, Dynamic-VPN, Firewall Authentication Pass-Through with Web-Redirect and Zero Touch Provisioning. An unauthenticated attacker can read files, inject commands into a log or obtain J-Web session tokens. CISA lists it as known exploited.
Impact
Over the network and without credentials, an attacker can read world-readable files. On 19.3R1 and later, this includes the configuration file. The attacker can also inject commands into httpd.log, with limited effect because the service runs as 'nobody'. If J-Web is enabled, the attacker can gain the access of any logged-in J-Web user, including administrators. CISA rates technical impact as total and exploitation as not automatable. Devices with HTTP/HTTPS services disabled are not affected.
Who is affected
Juniper Networks Junos OS is affected across many branches, from 12.3 up to 20.1. Examples include 12.3 before 12.3R12-S16, 15.1 before 15.1R7-S7, and 17.3 before 17.3R3-S8. The CVE record lists further affected ranges as well. Fixed versions named in the record include 12.3R12-S16, 12.3X48-D101, 12.3X48-D105, 14.1X53-D54, 15.1R7-S7, 15.1X49-D211, 15.1X49-D220, 16.1R7-S8, 17.2R3-S4, 17.3R3-S8, 17.4R2-S11, 17.4R3-S2, 18.1R3-S10, 18.2R2-S7, 18.2R3-S4, 18.3R2-S4, 18.3R3-S2, 18.4R3-S2, 19.1R3-S1, 19.2R2, 19.3R2-S3, 19.3R3, 19.4R1-S2, 19.4R2, 20.1R1-S1 and 20.1R2.
Written with AI from the data on this page and checked against it automatically.
Official description
A vulnerability in the HTTP/HTTPS service used by J-Web, Web Authentication, Dynamic-VPN (DVPN), Firewall Authentication Pass-Through with Web-Redirect, and Zero Touch Provisioning (ZTP) allows an unauthenticated attacker to perform local file inclusion (LFI) or path traversal. Using this vulnerability, an attacker may be able to inject commands into the httpd.log, read files with 'world' readable permission file or obtain J-Web session tokens.
In the case of command injection, as the HTTP service runs as user 'nobody', the impact of this command injection is limited. (CVSS score 5.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) In the case of reading files with 'world' readable permission, in Junos OS 19.3R1 and above, the unauthenticated attacker would be able to read the configuration file.
(CVSS score 5.9, vector CVSS:3.1/ AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) If J-Web is enabled, the attacker could gain the same level of access of anyone actively logged into J-Web. If an administrator is logged in, the attacker could gain administrator access to J-Web.
(CVSS score 8.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) This issue only affects Juniper Networks Junos OS devices with HTTP/HTTPS services enabled. Junos OS devices with HTTP/HTTPS services disabled are not affected. If HTTP/HTTPS services are enabled, the following command will show the httpd processes: user@device> show system processes | match http 5260 - S 0:00.13 /usr/sbin/httpd-gk -N 5797 - I 0:00.10 /usr/sbin/httpd --config /jail/var/etc/httpd.conf To summarize: If HTTP/HTTPS services are disabled, there is no impact from this vulnerability.
If HTTP/HTTPS services are enabled and J-Web is not in use, this vulnerability has a CVSS score of 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N). If J-Web is enabled, this vulnerability has a CVSS score of 8.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
Juniper SIRT has received a single report of this vulnerability being exploited in the wild. Out of an abundance of caution, we are notifying customers so they can take appropriate actions. Indicators of Compromise: The /var/log/httpd.log may have indicators that commands have injected or files being accessed.
The device administrator can look for these indicators by searching for the string patterns "=*;*&" or "*%3b*&" in /var/log/httpd.log, using the following command: user@device> show log httpd.log | match "=*;*&|=*%3b*&" If this command returns any output, it might be an indication of malicious attempts or simply scanning activities. Rotated logs should also be reviewed, using the following command: user@device> show log httpd.log.0.gz | match "=*;*&|=*%3b*&" user@device> show log httpd.log.1.gz | match "=*;*&|=*%3b*&" Note that a skilled attacker would likely remove these entries from the local log file, thus effectively eliminating any reliable signature that the device had been attacked.
This issue affects Juniper Networks Junos OS 12.3 versions prior to 12.3R12-S16; 12.3X48 versions prior to 12.3X48-D101, 12.3X48-D105; 14.1X53 versions prior to 14.1X53-D54; 15.1 versions prior to 15.1R7-S7; 15.1X49 versions prior to 15.1X49-D211, 15.1X49-D220; 16.1 versions prior to 16.1R7-S8; 17.2 versions prior to 17.2R3-S4; 17.3 versions prior to 17.3R3-S8; 17.4 versions prior to 17.4R2-S11, 17.4R3-S2; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R2-S7, 18.2R3-S4; 18.3 versions prior to 18.3R2-S4, 18.3R3-S2; 18.4 versions prior to 18.4R1-S7, 18.4R3-S2 ; 18.4 version 18.4R2 and later versions; 19.1 versions prior to 19.1R1-S5, 19.1R3-S1; 19.1 version 19.1R2 and later versions; 19.2 versions prior to 19.2R2; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S2, 19.4R2; 20.1 versions prior to 20.1R1-S1, 20.1R2.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Juniper Networks Junos OSAffectedFixed in
- ≥ 12.3, < 12.3R12-S16
- ≥ 12.3X48, < 12.3X48-D105
- ≥ 14.1X53, < 14.1X53-D54
- ≥ 15.1, < 15.1R7-S7
- ≥ 15.1X49, < 15.1X49-D220
- ≥ 16.1, < 16.1R7-S8
- ≥ 17.2, < 17.2R3-S4
- ≥ 17.3, < 17.3R3-S8
- ≥ 17.4, < 17.4R3-S2
- ≥ 18.1, < 18.1R3-S10
- ≥ 18.2, < 18.2R3-S4
- ≥ 18.3, < 18.3R3-S2
- ≥ 18.4, < 18.4R3-S2
- ≥ 19.1, < 19.1R3-S1
- ≥ 19.2, < 19.2R2
- ≥ 19.3, < 19.3R3
- ≥ 19.4, < 19.4R2
- ≥ 20.1, < 20.1R2
- 12.3R12-S16
- 12.3X48-D101
- 12.3X48-D105
- 14.1X53-D54
- 15.1R7-S7
- 15.1X49-D211
- 15.1X49-D220
- 16.1R7-S8
- 17.2R3-S4
- 17.3R3-S8
- 17.4R2-S11
- 17.4R3-S2
- 18.1R3-S10
- 18.2R2-S7
- 18.2R3-S4
- 18.3R2-S4
- 18.3R3-S2
- 18.4R3-S2
- 19.1R3-S1
- 19.2R2
- 19.3R2-S3
- 19.3R3
- 19.4R1-S2
- 19.4R2
- 20.1R1-S1
- 20.1R2
| Product | Affected | Fixed in |
|---|---|---|
| Juniper Networks Junos OS |
|
|
How to fix it
- Update to a fixed version: 12.3R12-S16, 12.3X48-D101, 12.3X48-D105, 14.1X53-D54, 15.1R7-S7, 15.1X49-D211, 15.1X49-D220, 16.1R7-S8 and 18 more (see the table).
- Vendor advisory: kb.juniper.net/JSA11021
- CISA's deadline for US federal agencies: 2022-04-15 (passed) – a useful benchmark for everyone else, too.
Vendor solution:
- The following software releases have been updated to resolve this specific issue: 12.3R12-S16, 12.3X48-D101, 12.3X48-D105, 14.1X53-D54, 15.1X49-D211, 15.1X49-D220, 15.1R7-S7, 16.1R7-S8, 17.2R3-S4, 17.4R2-S11, 17.3R3-S8, 17.4R3-S2, 18.1R3-S10, 18.2R2-S7, 18.2R3-S4, 18.3R2-S4, 18.3R3-S2, 18.4R1-S7, 18.4R3-S2, 19.1R1-S5, 19.1R3-S1, 19.2R2, 19.3R2-S3, 19.3R3, 19.4R1-S2, 19.4R2, 20.1R1-S1, 20.1R2 and all subsequent releases.
- Note: At the time of this publication, the following fixed releases are available for customer download: 12.3X48-D101, 15.1X49-D211, 18.2R3-S4, 18.4R3-S2, and 20.1R1-S1, the remaining fixed releases will be available in future time. 12.3X48-D101 & 15.1X49-D211 releases can be downloaded from the below URLs: 12.3X48-D101 : Branch SRX-Series Install Package (for SRX100H2, SRX110HE2, SRX210H2, SRX220H2, SRX240H2, SRX550, SRX650): junos-srxsme-12.3X48-D101-domestic.tgz webdownload.juniper.net/swdl/dl/secure/site/1/record/1074… MD5 = b822376f7a385e74499b186cf28c122b SHA-1 = e6138e45bf9d29e962468e6e114e537142d4cc0d SHA-256 = b21a9ae9f5d0b0ec25180682193faba7bf54e836fda0eb78babd3df843f90e6a SRX 1000/3000-Series Install Package : junos-srx1k3k-12.3X48-D101-d…
Workaround:
- There are no viable workarounds for this issue.
- It is highly recommended to disable HTTP/HTTPS service and DVPN: user@device# deactivate system services web-management user@device# deactivate security dynamic-vpn (if DVPN is enabled) user@device# commit or allowing HTTP service only on from trusted hosts or networks (refer to kb.juniper.net/KB21265 for details on how to limite HTTP service).
What to do
- Upgrade Junos OS to a fixed release for your branch, such as
18.4R3-S2,19.3R3or20.1R2, following Juniper's advisory. - Check whether HTTP/HTTPS services are enabled. Disable them where they are not needed, since devices with these services disabled are not affected.
- Keep J-Web and other web services off the internet. Restrict access to trusted management networks.
- Review current and rotated httpd.log files for the indicators of compromise described in Juniper's advisory.
- If compromise is suspected, rotate credentials and review the device configuration, because session tokens and configuration files may have been exposed.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), CWE-73 External Control of File Name or Path
Questions about CVE-2020-1631
- Are devices with HTTP/HTTPS services disabled affected?
- No. Juniper states that Junos OS devices with HTTP/HTTPS services disabled are not affected. Only devices with these services enabled are at risk.
- Is this vulnerability exploited in the wild?
- Yes. Juniper SIRT received a report of exploitation in the wild. CISA added CVE-2020-1631 to its Known Exploited Vulnerabilities catalog on 2022-03-25, with a US federal due date of 2022-04-15.
- Can clean log files prove a device was not attacked?
- No. Juniper notes that a skilled attacker would likely remove the relevant entries from the local log file. A clean httpd.log therefore does not reliably rule out an attack.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.