Skip to main content
CISA Known Exploited Vulnerabilities

Juniper Junos OS Path Traversal Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2022-03-25
Remediation due
2022-04-15

Required action
Apply updates per vendor instructions.

CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2020-1631

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.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2020-1631 to the KEV catalog 690 days after its CVE record was published.
  • It is one of 8 Juniper entries in the CISA KEV catalog, and the only one added in 2022.
  • Its current EPSS score (4.9%) is higher than that of 16% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score8.8 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impacttotal

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
and forensic triage
Asset not publicly exposed
14 days
KEV due date
2022-04-15
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-02-07).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Juniper Networks
Junos OS
12.3 to <12.3R12-S16
12.3X48 to <12.3X48-D101, 12.3X48-D105
14.1X53 to <14.1X53-D54
15.1 to <15.1R7-S7
15.1X49 to <15.1X49-D211, 15.1X49-D220
16.1 to <16.1R7-S8
17.2 to <17.2R3-S4
17.3 to <17.3R3-S8
17.4 to <17.4R2-S11, 17.4R3-S2
18.1 to <18.1R3-S10
18.2 to <18.2R2-S7, 18.2R3-S4
18.3 to <18.3R2-S4, 18.3R3-S2
18.4 to <18.4R1-S7, 18.4R3-S2 (affected again ≥ 18.4R2)
19.1 to <19.1R1-S5, 19.1R3-S1 (affected again ≥ 19.1R2)
19.2 to <19.2R2
19.3 to <19.3R2-S3, 19.3R3
19.4 to <19.4R1-S2, 19.4R2
20.1 to <20.1R1-S1, 20.1R2

Solutions and Workarounds

from the CNA's CVE record

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 https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107438.html MD5 = b822376f7a385e74499b186cf28c122b SHA-1 = e6138e45bf9d29e962468e6e114e537142d4cc0d SHA-256 = b21a9ae9f5d0b0ec25180682193faba7bf54e836fda0eb78babd3df843f90e6a SRX 1000/3000-Series Install Package : junos-srx1k3k-12.3X48-D101-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107436.html MD5 = b93229ea43f66b539f22ecc5a9be0f07 SHA-1 = 2c625e9bc155b9fcb4c9a1a371bba473363ee6f0 SHA-256 = 982434f9cde9492e1d80d14c43a7cdcc5261db15a11f65fa7c9881a0fc0cd3db SRX5000-Series Install Package: junos-srx5000-12.3X48-D101-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107437.html MD5 = 7dc73801b7680fda42d453d6d3d6f10c SHA-1 = 05f1eda5ec112c7e2afeebea4d47c007e0a8bd60 SHA-256 = 88d40e4b6b949a5c656c2b5fffa3adb41fe4943fb3e5d9cfaa439e603889e839 15.1X49-D211: SRX300 & SRX500-Series Install Package: junos-srxsme-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107439.html MD5 = dfd3428c7f83eb11142bbe32bac2a151 SHA-1 = a22f0ead795c8afb0a4d59d1b9b785c83801cd65 SHA-256 = dc42e24db0e2af7b2e6aaafdaa61f8e658fabc91c8a888efad586a5fbd2fa29a SRX1500 Install Package: junos-srxentedge-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107442.html MD5 = 348f2fcd96b31d51b9d71147d09fabd8 SHA-1 = cf8ee775ca1ca12706975fdd0748c1967732c2fe SHA-256 = 62d460ea531161936f0ac75fa4501bc6cadb700388bdb93b7e706a09e985eff5 SRX4100 and SRX4200 Install Package: junos-srxmr-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107441.html MD5 = 55b4c96b05b5fd9595a8ee071dbbf438 SHA-1 = ae6d7978964c3be6b632033b3616208e47653617 SHA-256 = 20274c3b66d4b54471684a5f534abe0ba1d8bebabbb6f78f0028fcc275076df1 SRX5000 Series Install Package: junos-srx5000-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107440.html MD5 = b918fa5a341815ccdb230560539e8725 SHA-1 = 38e912a55f1407e18e1bb8305f854fcd97c1adcb SHA-256 = c1aaafdd9b23a525236c414e4cf213542246326317070b5e98ac5cccc5fa1e72 vSRX Upgrade TGZ: junos-vsrx-15.1X49-D211-domestic.tgz https://webdownload.juniper.net/swdl/dl/secure/site/1/record/107452.html MD5 = 55b4c96b05b5fd9595a8ee071dbbf438 SHA-1 = ae6d7978964c3be6b632033b3616208e47653617 SHA-256 = 20274c3b66d4b54471684a5f534abe0ba1d8bebabbb6f78f0028fcc275076df1

Workarounds

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 https://kb.juniper.net/KB21265 for details on how to limite HTTP service).

References

1 links

Record Details

Publicly disclosed
2020-04-27
Published
2020-05-04
Last updated
2025-10-21
Assigner (CNA)
juniper
Credited to
The Juniper SIRT would like to would like to acknowledge and thank Laing Bian and Leishen Song (@rayh4c) of 360 ATA for reporting this issue.

More from Juniper Networks

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.