dbcve.org
JettyApplication · Eclipse

CVE-2025-1948

HIGH · 7.5 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to 12.0.17 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Eclipse Jetty versions 12.0.0 to 12.0.16 included, an HTTP/2 client can specify a very large value for the HTTP/2 settings parameter SETTINGS_MAX_HEADER_LIST_SIZE. The Jetty HTTP/2 server does not perform validation on this setting, and tries to allocate a ByteBuffer of the specified capacity to encode HTTP responses, likely resulting in OutOfMemoryError being thrown, or even the JVM process exiting.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Eclipse Jetty 12.0.0-12.0.16, the HTTP/2 server does not validate the SETTINGS_MAX_HEADER_LIST_SIZE parameter sent by clients. A malicious client can specify an excessively large value, causing the server to attempt allocating a ByteBuffer of that size to encode responses, resulting in OutOfMemoryError or JVM crash.

MitigationUpgrade Jetty to version 12.0.17 or later which includes validation for this setting, or implement a proxy-level limit on HTTP/2 settings parameters before they reach the Jetty server.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JettyApplication
Affected:>= 12.0.0, < 12.0.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jetty installation and version
    Locate the jetty-version.jar or check your build/packaging manifest for the Eclipse Jetty version. Common locations: lib/jetty-version.jar, or examine the jetty-http.jar META-INF/MANIFEST.MF for Implementation-Version
    Affected if The installed version is 12.0.0 through 12.0.16 inclusive
  2. Confirm HTTP/2 protocol is enabled
    Examine your Jetty configuration XML files (start.d/*.ini, jetty.xml, or equivalent) for HTTP/2 connector configuration. Look for org.eclipse.jetty.http2.HTTP2CConnector or org.eclipse.jetty.http2.server.HTTP2ServerConnector
    Affected if An HTTP/2 connector is configured and the server accepts HTTP/2 connections
  3. Verify server accepts external connections
    Review network listener configuration to confirm the HTTP/2 port is bound to a reachable interface (0.0.0.0 or external IP) rather than localhost only
    Affected if The HTTP/2 port is exposed to untrusted network segments or the public internet
  4. Check for custom SETTINGS_MAX_HEADER_LIST_SIZE limits
    Inspect your Jetty HTTP/2 connector configuration for any custom maxHeaderListSize settings. Look for Set<Configuration.Factory> or similar configuration that may explicitly limit header list sizes
    Affected if No explicit limit on SETTINGS_MAX_HEADER_LIST_SIZE is configured, allowing clients to send unbounded values

You are affected if you run Jetty 12.0.0-12.0.16 with an exposed HTTP/2 connector and have not implemented external validation or limits on the SETTINGS_MAX_HEADER_LIST_SIZE parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.0.17 or later
Fixed in 12.0.17
Interim mitigation

Upgrade Jetty to version 12.0.17 or later which includes validation for this setting, or implement a proxy-level limit on HTTP/2 settings parameters before they reach the Jetty server.

Recommended fix High confidence

12.0.17

  1. Upgrade Eclipse Jetty from version 12.0.0 - 12.0.16 to version 12.0.17 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jetty Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1948 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data