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.
CVE-2020-1631
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
Also known asEUVD-2020-12499 (ENISA EUVD) · GHSA-g762-xhjq-x42p (GitHub Security Advisories)Source: ENISA EUVD
- Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
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,… (from the CVE record's solution, Juniper Networks, Inc.) — apply it.
- CVSS v3
- 8.8
- EG Score
- 9.8CRITICALhigh confidence
- EG Risk
- 84EG Risk 84/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation100% × 40%Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: 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,… (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact. - EPSS PROB
- 4.9%
- EPSS %ILE
- 92nd
- KEV
- ⚠ Exploited
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 4.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.
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,… (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.
The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
CISA required action“Apply updates per vendor instructions.”
Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2020-1631
Published
May 4, 2020
Last Modified
October 24, 2025
Advisory Details (2)
Auto-updated Oct 26, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-1631Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 130× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 100 of 1,079 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 979 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 02:54 UTCEG score recompute
- 2026-11-02 02:54 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub severity MODERATE · GitHub CVSS 9.8
- 2026-11-01 16:29 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-11-01 00:36 UTCEG score recompute
- 2026-11-01 00:36 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-31 16:28 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-30 22:19 UTCEG score recompute
- 2026-10-30 22:19 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-30 16:29 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-29 20:03 UTCEG score recompute
- 2026-10-29 20:03 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-29 16:28 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-28 17:46 UTCEG score recompute
- 2026-10-28 17:46 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-28 16:27 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-27 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-27 15:30 UTCEG score recompute
- 2026-10-27 15:29 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-26 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-26 13:11 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-25 18:49 UTCEG score recompute
- 2026-10-25 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-25 10:53 UTCEG score recompute
- 2026-10-25 10:53 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-24 16:28 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
Show 75 moreShow fewer
- 2026-10-24 08:36 UTCEG score recompute
- 2026-10-24 08:36 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-23 16:27 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-23 06:19 UTCEG score recompute
- 2026-10-23 06:19 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-22 16:29 UTCEPSS rescoreEPSS 4.9% · 92nd percentile
- 2026-10-22 04:02 UTCEG score recompute
- 2026-10-22 04:02 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-21 01:43 UTCEG score recompute
- 2026-10-21 01:43 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-20 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-19 23:27 UTCEG score recompute
- 2026-10-19 23:27 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-19 16:27 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-18 21:10 UTCEG score recompute
- 2026-10-18 21:10 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 4.9% · 91st percentile
- 2026-10-18 09:32 UTCEG score recompute
- 2026-10-17 18:53 UTCEG score recompute
- 2026-10-17 18:53 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-17 16:28 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-16 16:35 UTCEG score recompute
- 2026-10-16 16:35 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-16 16:33 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-15 16:27 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-15 14:11 UTCEG score recompute
- 2026-10-15 14:10 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-14 16:28 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-14 11:51 UTCEG score recompute
- 2026-10-14 11:51 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-13 16:28 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-13 09:33 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-12 19:44 UTCEG score recompute
- 2026-10-12 16:29 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-12 07:14 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-12 02:47 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-11 22:23 UTCEG score recompute
- 2026-10-11 22:23 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-11 17:59 UTCEG score recompute
- 2026-10-11 17:59 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-11 13:43 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-11 13:34 UTCEG score recompute
- 2026-10-11 13:33 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-11 09:05 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-11 04:40 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-11 00:16 UTCEG score recompute
- 2026-10-11 00:15 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-10 19:50 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-10 15:26 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-10 11:01 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-10 06:36 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-10 02:12 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-09 21:48 UTCEG score recompute
- 2026-10-09 21:48 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-09 17:22 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-09 12:55 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-09 08:29 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-09 04:05 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-08 23:40 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-08 19:16 UTCEG score recompute
- 2026-10-08 19:15 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-08 16:38 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-08 14:51 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-08 10:23 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-08 05:58 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-08 01:33 UTCEG score recompute
- 2026-10-08 01:33 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-07 23:44 UTCEPSS rescoreEPSS 4.8% · 91st percentile
- 2026-10-07 21:08 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-07 16:43 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-07 12:19 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
- 2026-10-07 07:55 UTCGHSA enrichmentGHSA-g762-xhjq-x42p · GitHub CVSS 9.8
Related CVEs(same CWE)
Same CWE
10 shownCWE-22
Frequently asked(6)
What is CVE-2020-1631?
When was CVE-2020-1631 made public?
Is CVE-2020-1631 actively exploited?
What is the CVSS score of CVE-2020-1631?
Which products are affected by CVE-2020-1631?
How do I remediate CVE-2020-1631?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2020-1631
Is Your Infrastructure Affected by CVE-2020-1631?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.