CVE-2019-17638
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
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
rank 47 = 17 + 24 + 1 + 5 + 0
rank@v1 · this cycle
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.11138 · without this subject the record ranks 30
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 9.4, from NVD · without this subject the record ranks 23
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
rose on 2025-10-04 · without this subject the record ranks 46
How much of the world it touches
NVD CPE configurations
3 products in the CPE ranges · without this subject the record ranks 42
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 47
$516,000 = $4.99M incident cost x 0.9280467328949208 exposure x 0.11138 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
Hindsight · the state
Foresight · where to check next
No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.
Running The Eclipse Foundation Eclipse Jetty? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Proof-of-concept published · 1 public repository, 2021-02-04.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published · 1 public repository2021-02-04receipt
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
What it is stated by the CNA
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. receipt
Read the rest of the CNA's description
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).
NVD's analysis a second authority
- severity
- 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
- weakness
- CWE-672; CWE-675
- affected versions
- eclipse jetty 9.4.27; eclipse jetty 9.4.28; eclipse jetty 9.4.29
check it yourself bugs.eclipse.org openwall.com lists.fedoraproject.org lists.apache.org lists.apache.org lists.apache.org +11 morereceipt
Dated events
Movement the material steps
Show all 54 observations
54 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2019-17638.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.