CVE-2019-17638

CRITICALNVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 11% (95th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 11%CVSS: 9.4Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with other data. Thread1 then proceeds to write the buffer that now contains different data. This results in client1, which issued request1 seeing data from another request or response which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.). If the Jetty version cannot be upgraded, the vulnerability can be significantly reduced by configuring a responseHeaderSize significantly larger than the requestHeaderSize (12KB responseHeaderSize and 8KB requestHeaderSize).

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
63
EG Risk 63/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity94% × 45%
Exploitation40% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
11%
EPSS %ILE
95th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 9, 2020

Last Modified

November 21, 2024

Advisory Details (10)

Auto-updated Oct 2, 2026
Patch available.
generic

Pony Mail

https://lists.apache.org/thread.html/r9a2cfa56d30782a0c17a5deb951a622d1f5c8de48e1c3b578ffc2a84%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r9584c4304c888f651d214341a939bd264ed30c9e3d0d30fe85097ecf%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r81f58591fb4716fb867b36956f30c7c8ad4ab3f23abc952d9d86a2a0%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r7fc5f2ed49641ea91c433e3cd0fc3d31c0278c87b82b15c33b881415%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r521168299e023fb075b57afe33d17ff1d09e8a10e0fd8c775ea0e028%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r4bdd3f7bb6820a79f9416b6667d718a06d269018619a75ce4b759318%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r378e4cdec15e132575aa1dcb6296ffeff2a896745a8991522e266ad4%40%3Ccommits.pulsar.apache.org%3E
generic

Pony Mail

https://lists.apache.org/thread.html/r29073905dc9139d0d7a146595694bf57bb9e35e5ec6aa73eb9c8443a%40%3Ccommits.pulsar.apache.org%3E
generic

oss-security - Vulnerability in Jenkins

http://www.openwall.com/lists/oss-security/2020/08/17/1
generic

564984 – (CVE-2019-17638) CVE Request: Jetty Corrupt Response Buffer

https://bugs.eclipse.org/bugs/show_bug.cgi?id=564984

Vendor Advisories for CVE-2019-17638(5)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjetty2020-12-16redhat
redhatjenkins-0:2.235.5.1600415953-1.el72020-10-22redhat
redhatopenshift4/ose-jenkins:v4.4.0-202009260441.p02020-10-13redhat
redhatjenkins-0:2.235.5.1600414805-1.el72020-09-30redhat
redhatjenkins-0:2.235.5.1600415514-1.el72020-09-23redhat

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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jetty9—
  • every version up to 9.4.31-1: fixed in 9.4.31-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jetty9—
  • every version up to 9.4.31-1: fixed in 9.4.31-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jetty9—
  • every version up to 9.4.31-1: fixed in 9.4.31-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jetty9—
  • every version up to 9.4.31-1: fixed in 9.4.31-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.eclipse.jetty:jetty-server9.4.27.v20200227, 9.4.28.v20200408, 9.4.29.v20200521
  • 9.4.27 up to 9.4.30.v20200611: fixed in 9.4.30.v20200611
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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.

Showing the most recent 100 of 143 total refreshes for this CVE.

  1. 2026-10-09 20:03 UTCEPSS rescore
  2. 2026-10-08 16:37 UTCEPSS rescore
  3. 2026-10-07 23:43 UTCEPSS rescore
  4. 2026-10-06 15:12 UTCEPSS rescore
  5. 2026-10-05 17:39 UTCEPSS rescore
  6. 2026-10-03 14:22 UTCEPSS rescore
  7. 2026-09-30 14:59 UTCEPSS rescore
  8. 2026-09-30 10:14 UTCEG score recompute
  9. 2026-09-27 13:40 UTCEPSS rescore
  10. 2026-09-26 21:12 UTCOSV refresh
  11. 2026-09-26 15:54 UTCEPSS rescore
  12. 2026-09-26 15:54 UTCEPSS rescore
  13. 2026-09-26 00:20 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-23 13:43 UTCEPSS rescore
  16. 2026-09-22 14:43 UTCEPSS rescore
  17. 2026-09-21 20:28 UTCEPSS rescore
  18. 2026-09-20 20:10 UTCEPSS rescore
  19. 2026-09-18 19:22 UTCEPSS rescore
  20. 2026-09-17 19:22 UTCEPSS rescore
  21. 2026-09-16 14:04 UTCEPSS rescore
  22. 2026-09-15 03:05 UTCEPSS rescore
  23. 2026-09-12 14:56 UTCEPSS rescore
  24. 2026-09-11 14:48 UTCEPSS rescore
  25. 2026-09-11 09:32 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 15:57 UTCEPSS rescore
  2. 2026-09-07 07:18 UTCOSV refresh
  3. 2026-09-06 13:44 UTCEPSS rescore
  4. 2026-09-05 15:24 UTCEPSS rescore
  5. 2026-09-04 13:56 UTCEPSS rescore
  6. 2026-09-02 14:07 UTCEPSS rescore
  7. 2026-09-01 03:32 UTCEPSS rescore
  8. 2026-08-30 19:13 UTCEPSS rescore
  9. 2026-08-30 01:18 UTCEPSS rescore
  10. 2026-08-28 21:36 UTCEPSS rescore
  11. 2026-08-27 14:21 UTCEPSS rescore
  12. 2026-08-26 14:42 UTCEPSS rescore
  13. 2026-08-25 13:45 UTCEPSS rescore
  14. 2026-08-24 14:11 UTCEPSS rescore
  15. 2026-08-21 23:45 UTCEPSS rescore
  16. 2026-08-20 22:51 UTCEPSS rescore
  17. 2026-08-20 16:31 UTCOSV refresh
  18. 2026-08-19 17:00 UTCEPSS rescore
  19. 2026-08-18 13:44 UTCEPSS rescore
  20. 2026-08-16 14:52 UTCEPSS rescore
  21. 2026-08-16 02:10 UTCEPSS rescore
  22. 2026-08-15 01:26 UTCEPSS rescore
  23. 2026-08-12 13:47 UTCEPSS rescore
  24. 2026-08-09 13:43 UTCEPSS rescore
  25. 2026-08-08 16:33 UTCEPSS rescore
  26. 2026-08-07 16:23 UTCEPSS rescore
  27. 2026-08-06 13:43 UTCEPSS rescore
  28. 2026-08-05 19:13 UTCEPSS rescore
  29. 2026-08-05 10:40 UTCOSV refresh
  30. 2026-08-04 15:05 UTCEPSS rescore
  31. 2026-08-02 02:23 UTCEPSS rescore
  32. 2026-08-01 04:12 UTCEPSS rescore
  33. 2026-07-30 16:24 UTCEPSS rescore
  34. 2026-07-30 01:27 UTCEPSS rescore
  35. 2026-07-28 15:32 UTCEPSS rescore
  36. 2026-07-25 14:14 UTCEPSS rescore
  37. 2026-07-24 14:14 UTCEPSS rescore
  38. 2026-07-24 14:14 UTCEPSS rescore
  39. 2026-07-23 14:15 UTCEPSS rescore
  40. 2026-07-23 01:42 UTCEG score recompute
  41. 2026-07-22 22:22 UTCEG score recompute
  42. 2026-07-22 14:05 UTCEPSS rescore
  43. 2026-07-21 15:22 UTCEPSS rescore
  44. 2026-07-21 15:22 UTCEPSS rescore
  45. 2026-07-20 17:04 UTCEPSS rescore
  46. 2026-07-20 17:04 UTCEPSS rescore
  47. 2026-07-19 14:28 UTCEPSS rescore
  48. 2026-07-19 14:28 UTCEPSS rescore
  49. 2026-07-19 09:22 UTCOSV refresh
  50. 2026-07-19 02:26 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-18 10:01 UTCEPSS rescore
  53. 2026-07-16 16:59 UTCEPSS rescore
  54. 2026-07-16 16:59 UTCEPSS rescore
  55. 2026-07-15 16:55 UTCEPSS rescore
  56. 2026-07-15 16:55 UTCEPSS rescore
  57. 2026-07-13 22:27 UTCEPSS rescore
  58. 2026-07-12 05:43 UTCEPSS rescore
  59. 2026-07-12 05:43 UTCEPSS rescore
  60. 2026-07-11 08:24 UTCEPSS rescore
  61. 2026-07-11 08:24 UTCEPSS rescore
  62. 2026-07-09 19:06 UTCEPSS rescore
  63. 2026-07-08 15:11 UTCEPSS rescore
  64. 2026-07-07 13:43 UTCEPSS rescore
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 16:25 UTCEPSS rescore
  67. 2026-07-06 02:20 UTCEPSS rescore
  68. 2026-07-05 02:27 UTCEPSS rescore
  69. 2026-07-04 06:28 UTCEPSS rescore
  70. 2026-07-01 15:03 UTCOSV refresh
  71. 2026-07-01 15:03 UTCEPSS rescore
  72. 2026-07-01 15:03 UTCEPSS rescore
  73. 2026-06-30 23:20 UTCEPSS rescore
  74. 2026-06-29 14:03 UTCEPSS rescore
  75. 2026-06-28 14:04 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2019-17638?
CVE-2019-17638 is a critical vulnerability published on July 9, 2020. In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double…
When was CVE-2019-17638 disclosed?
CVE-2019-17638 was first published on July 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-17638 actively exploited?
CVE-2019-17638 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-17638?
CVE-2019-17638 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2019-17638?
A fix for CVE-2019-17638 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-17638 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-17638

Explore →

Is Your Infrastructure Affected by CVE-2019-17638?

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

Book a Demo →Browse All CVEs