Skip to content
Noroxi
CVE-2019-17638· NVD / CVE Program· CNA eclipse

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

Noroxi assessment

Priority: Plan (action score 40/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 11.1% (FIRST EPSS); higher than 95.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: jetty9 (Debian:12) 9.4.31-1; org.eclipse.jetty:jetty-server (Maven) 9.4.30.v20200611; jenkins (Red Hat:openshift:3.11::el7) 0:2.235.5.1600415953-1.el7.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to jetty9 (Debian:12) 9.4.31-1; org.eclipse.jetty:jetty-server (Maven) 9.4.30.v20200611; jenkins (Red Hat:openshift:3.11::el7) 0:2.235.5.1600415953-1.el7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

CriticalCVSS 9.4 · v3.1—Proof of concept Fix available
Published
Jul 9, 2020
Updated
Jun 16, 2026
EPSS
11.1% · 95th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
37 / 40 · 9.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 11.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-17638

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for eclipse records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
eclipsejetty

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • eclipse jetty9.4.27
  • eclipse jetty9.4.28
  • eclipse jetty9.4.29

Versions reported by the vendor

Affected version ranges reported by the assigning authority (eclipse). Independent of NVD's CPE analysis and usually ahead of it.

  • The Eclipse Foundation Eclipse Jetty

    • 9.4.27.v20200227 to 9.4.29.v20200521affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12jetty9before 9.4.31-19.4.31-1
Mavenorg.eclipse.jetty:jetty-serverfrom 9.4.27 · before 9.4.30.v202006119.4.30.v20200611
Red Hat:openshift:3.11::el7jenkinsbefore 0:2.235.5.1600415953-1.el70:2.235.5.1600415953-1.el7
Red Hat:openshift:4.3::el7jenkinsbefore 0:2.235.5.1600415514-1.el70:2.235.5.1600415514-1.el7
Red Hat:openshift:4.3::el8openshiftbefore 0:4.3.37-202009120213.p0.git.0.dffefe4.el80:4.3.37-202009120213.p0.git.0.dffefe4.el8
Red Hat:openshift:4.3::el8openshift-hyperkubebefore 0:4.3.37-202009120213.p0.git.0.dffefe4.el80:4.3.37-202009120213.p0.git.0.dffefe4.el8
Red Hat:openshift:4.5::el7jenkinsbefore 0:2.235.5.1600414805-1.el70:2.235.5.1600414805-1.el7

Same product

eclipse: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-34429For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the con
    60This week
  • CVE-2021-28164In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segm
    60This week
  • CVE-2015-2080The exception handling code in Eclipse Jetty before 9.2.9.v20150224 allows remote attackers to obtain sensitive information from process mem
    53Plan

Published before and after this one in the same product

  • ← EarlierCVE-2009-5046Nov 6, 2019 · JSP Dump and Session Dump Servlet XSS in jetty before 6.1.22.
    24Monitor
  • ← EarlierCVE-2019-17632Nov 25, 2019 · In Eclipse Jetty versions 9.4.21.v20190926, 9.4.22.v20191022, and 9.4.23.v20191118, the generation of default unhandled Error response conte
    25Monitor
  • Later →CVE-2020-27216Oct 23, 2020 · In Eclipse Jetty versions 1.0 thru 9.4.32.v20200930, 10.0.0.alpha1 thru 10.0.0.beta2, and 11.0.0.alpha1 thru 11.0.0.beta2O, on Unix like sys
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:jetty99.4.31-1 · Debian:12Package registry (OSV)
Maven:org.eclipse.jetty:jetty-server9.4.30.v20200611Package registry (OSV)
red hat:jenkins0:2.235.5.1600415514-1.el7 · Red Hat:openshift:4.3::el7Package registry (OSV)
red hat:openshift0:4.3.37-202009120213.p0.git.0.dffefe4.el8 · Red Hat:openshift:4.3::el8Package registry (OSV)
red hat:openshift-hyperkube0:4.3.37-202009120213.p0.git.0.dffefe4.el8 · Red Hat:openshift:4.3::el8Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12021-02-04

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+209 d
  3. TodayOct 25, 2026+2299 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-672 · Operation on a Resource after Expiration or Release

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (16 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records