CVE-2019-20372

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 15%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
96.3%
KEV
Not listed

Published

January 9, 2020

Last Modified

November 21, 2024

References (22)

Vendor Advisories for CVE-2019-20372(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunginx-light (1.4.6-1ubuntu3.9+esm1) @ trusty2026-05-27ubuntu
ubuntunginx-light (1.14.0-0ubuntu1.7) @ bionic2026-05-27ubuntu
redhatansible-tower-36/ansible-tower:3.6.7-12021-03-09redhat
redhatansible-tower-37/ansible-tower-rhel7:3.7.5-12021-03-09redhat
redhatnginx:1.16-8030020201124104955.229f0a1c2020-12-15redhat
redhatrh-nginx116-nginx-1:1.16.1-4.el7.12020-07-02redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-11 08:24 UTCEPSS rescore
  3. 2026-07-09 19:06 UTCEPSS rescore
  4. 2026-07-08 15:11 UTCEPSS rescore
  5. 2026-07-07 13:43 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-05 02:27 UTCEPSS rescore
  8. 2026-07-04 06:28 UTCEPSS rescore
  9. 2026-07-02 12:46 UTCOSV refresh
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-29 14:03 UTCEPSS rescore
  14. 2026-06-28 14:04 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-25 13:47 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
Show 35 more
  1. 2026-06-19 19:23 UTCEPSS rescore
  2. 2026-06-19 19:23 UTCEPSS rescore
  3. 2026-06-18 17:50 UTCEPSS rescore
  4. 2026-06-17 17:50 UTCEPSS rescore
  5. 2026-06-16 17:50 UTCEPSS rescore
  6. 2026-06-15 17:45 UTCEPSS rescore
  7. 2026-06-14 23:15 UTCEPSS rescore
  8. 2026-06-14 23:15 UTCEPSS rescore
  9. 2026-06-14 11:13 UTCOSV refresh
  10. 2026-06-13 22:58 UTCEPSS rescore
  11. 2026-06-12 23:09 UTCEPSS rescore
  12. 2026-06-11 13:58 UTCEPSS rescore
  13. 2026-06-10 22:16 UTCEPSS rescore
  14. 2026-06-05 22:45 UTCEPSS rescore
  15. 2026-06-05 22:45 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-05 06:08 UTCEPSS rescore
  18. 2026-06-04 13:10 UTCEPSS rescore
  19. 2026-06-04 13:10 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-01 13:50 UTCEPSS rescore
  23. 2026-06-01 13:50 UTCEPSS rescore
  24. 2026-05-31 22:29 UTCEPSS rescore
  25. 2026-05-31 22:29 UTCEPSS rescore
  26. 2026-05-31 00:14 UTCEPSS rescore
  27. 2026-05-31 00:14 UTCEPSS rescore
  28. 2026-05-29 13:42 UTCEPSS rescore
  29. 2026-05-28 13:43 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-27 09:25 UTCEG score recompute
  32. 2026-05-27 09:25 UTCVendor advisory
  33. 2026-05-27 09:25 UTCGHSA enrichment
  34. 2026-05-26 13:42 UTCEPSS rescore
  35. 2026-05-26 13:42 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xleft/CVE-2019-20372
    First seen Sep 16, 2023

    nginx http request smugling error_page directive

    Open source ↗

Frequently asked(5)

What is CVE-2019-20372?
CVE-2019-20372 is a medium vulnerability published on January 9, 2020. NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer.
When was CVE-2019-20372 disclosed?
CVE-2019-20372 was first published in the National Vulnerability Database on January 9, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-20372 actively exploited?
CVE-2019-20372 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-20372?
CVE-2019-20372 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2019-20372?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-20372, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-20372

Explore →

Is Your Infrastructure Affected by CVE-2019-20372?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs