dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-22201

HIGH · 7.5 CVSS v3.1 Published 2024-02-26
Fix available
A fix is available. Upgrade to 9.4.54 / 10.0.20 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
Jetty is a Java based web server and servlet engine. An HTTP/2 SSL connection that is established and TCP congested will be leaked when it times out. An attacker can cause many connections to end up in this state, and the server may run out of file descriptors, eventually causing the server to stop accepting new connections from valid clients. The vulnerability is patched in 9.4.54, 10.0.20, 11.0.20, and 12.0.6.

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

Jetty HTTP/2 SSL connections are leaked when they timeout while experiencing TCP congestion. Attackers can repeatedly trigger these leaked connections to exhaust server file descriptors, causing denial of service.

MitigationUpgrade Jetty to version 9.4.54, 10.0.20, 11.0.20, or 12.0.6 to patch the connection leak. Consider implementing connection rate limiting as a temporary mitigation.

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
Debian LinuxOperating system
Affected:= 10.0
Active Iq Unified ManagerApplication
Affected:all versions
JettyApplication
Affected:>= 9.3.0, < 9.4.54>= 10.0.0, < 10.0.20>= 11.0.0, < 11.0.20>= 12.0.0, < 12.0.6
BluexpApplication
Affected:all versions

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 version
    Locate the jetty-version.jar or jetty-core jar and run: java -jar jetty-version.jar or inspect the META-INF/MANIFEST.MF file in the jetty-core jar for the Implementation-Version attribute
    Affected if The installed version falls within >= 9.3.0 and < 9.4.54, >= 10.0.0 and < 10.0.20, >= 11.0.0 and < 11.0.20, or >= 12.0.0 and < 12.0.6
  2. Confirm HTTP/2 connector is configured
    Inspect the Jetty XML configuration files (start.d/*.ini, jetty.xml, or similar) for HTTP/2Connector or Http2Configuration definitions in the Server Connectors section
    Affected if An Http2Connector or HTTP/2 protocol is explicitly configured on any server connector
  3. Verify SSL/TLS is enabled on the HTTP/2 connector
    Check the connector configuration for sslContextFactory or SslConnectionFactory definitions, and confirm the connector uses HTTPS or the ssl attribute is set
    Affected if SSL/TLS is enabled on the HTTP/2 connector (the vulnerability affects HTTP/2 over SSL only)
  4. Check for abnormal file descriptor growth
    Monitor the process file descriptor count over time using: ls -la /proc/<jetty-pid>/fd | wc -l (Linux) or equivalent process monitor. Observe if the count steadily increases without recycling
    Affected if File descriptors are continuously growing and not being released, indicating a connection leak

The environment is affected if running a vulnerable Jetty version AND HTTP/2 over SSL is enabled, as the leak only occurs under those specific conditions.

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 9.4.54 / 10.0.20 / 11.0.20 or later
Fixed in 9.4.5410.0.2011.0.20
Interim mitigation

Upgrade Jetty to version 9.4.54, 10.0.20, 11.0.20, or 12.0.6 to patch the connection leak. Consider implementing connection rate limiting as a temporary mitigation.

Recommended fix High confidence

Upgrade to Jetty 9.4.54+, 10.0.20+, 11.0.20+, or 12.0.6+ (choose the major version line matching your current deployment)

  1. Identify the current Jetty version installed in the environment
  2. For Jetty 9.x: Upgrade to version 9.4.54 or later
  3. For Jetty 10.x: Upgrade to version 10.0.20 or later
  4. For Jetty 11.x: Upgrade to version 11.0.20 or later
  5. For Jetty 12.x: Upgrade to version 12.0.6 or later
  6. Verify the upgrade was successful by checking the Jetty version
  7. Monitor file descriptor usage to confirm the resource leak is resolved
  8. For Active Iq Unified Manager and Bluexp: Contact vendor for specific patched releases (they support Jetty internally)
Caveat Major version upgrades (e.g., 9.x to 10.x, 10.x to 11.x, 11.x to 12.x) may introduce API changes; review Jetty migration guides before upgrading

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22201 — 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-2024-22201 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