dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-2048

HIGH · 7.5 CVSS v3.1 Published 2022-07-07
Fix available
A fix is available. Upgrade to 2.263 / 2.361.1 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 HTTP/2 server implementation, when encountering an invalid HTTP/2 request, the error handling has a bug that can wind up not properly cleaning up the active connections and associated resources. This can lead to a Denial of Service scenario where there are no enough resources left to process good requests.

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 HTTP/2 server implementation, when processing invalid HTTP/2 requests, the error handling routine fails to properly clean up active connections and associated resources. This resource leak accumulates over multiple malformed requests, eventually exhausting available resources and preventing legitimate requests from being processed, resulting in a Denial of Service.

MitigationUpgrade Eclipse Jetty to a version that includes the fix for CVE-2022-2048. Additionally, consider implementing request rate limiting and connection limits as a defense-in-depth measure while the upgrade is being planned.

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= 11.0
JenkinsApplication
Affected:< 2.263< 2.361.1
JettyApplication
Affected:< 9.4.47>= 10.0.0, < 10.0.9>= 11.0.0, < 11.0.9
Element Plug In For Vcenter ServerApplication
Affected:all versions
Management Services For Element Software And Netapp HciApplication
Affected:all versions
SnapcenterApplication
Affected:all versions
Solidfire \& Hci Storage NodeApplication
Affected:all versions
Hci Compute NodeHardware / appliance
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 if Jetty is in use
    Check for Jetty JAR files in the application's lib or dependencies folder, or examine the Maven/Gradle dependencies for org.eclipse.jetty entries. For Jenkins, check the included winstone.jar or Jetty libraries in JENKINS_HOME/war.</how
    Affected if Jetty libraries or dependencies are present in the deployment
  2. Determine the Jetty version
    Examine the Jetty JAR manifest (META-INF/MANIFEST.MF) for the Implementation-Version attribute, or check the specific jetty-version.txt file. For Jenkins, run 'java -jar jenkins.war --version' or check the bundled Jetty version in the war file.</how
    Affected if The Jetty version falls outside the fixed versions: not 9.4.47+, not 10.0.9+, and not 11.0.9+
  3. Verify HTTP/2 support is enabled
    Check the Jetty configuration XML files (such as start.d/http2.ini or jetty-http2.xml) for enabled HTTP/2 connectors. In code, verify Http2ConnectionFactory is used in the ServerConnector setup.</how
    Affected if HTTP/2 protocol support is configured and active on any Jetty connector
  4. Monitor for accumulating connections under malformed request load
    Observe active connection counts via netstat or server monitoring tools during periods of invalid HTTP/2 traffic. Compare connection counts before and after exposing the server to malformed requests.</how
    Affected if Connection counts grow without cleanup and do not return to baseline after malformed requests cease

A user is affected if they run a Jetty version below 9.4.47 / 10.0.9 / 11.0.9 with HTTP/2 protocol enabled, and they observe connection or resource accumulation under malformed HTTP/2 request 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 2.263 / 2.361.1 / 9.4.47 or later
Fixed in 2.2632.361.19.4.47
Interim mitigation

Upgrade Eclipse Jetty to a version that includes the fix for CVE-2022-2048. Additionally, consider implementing request rate limiting and connection limits as a defense-in-depth measure while the upgrade is being planned.

Recommended fix High confidence

Jetty 9.4.47+ / 10.0.9+ / 11.0.9+; Jenkins 2.363+ / 2.361.1+

  1. Identify the Jetty or Jenkins version currently in use by checking the application's dependencies or version manifest
  2. For Jetty: Upgrade to version 9.4.47, 10.0.9, or 11.0.9 (or later) depending on the major version line in use
  3. For Jenkins: Upgrade to version 2.263 (LTS) or 2.361.1 (LTS) or later
  4. For Debian systems: Update the jetty package via 'apt-get update && apt-get upgrade' to receive the patched version
  5. After upgrade, restart the affected services to load the fixed version
  6. Monitor system resources and HTTP/2 connection handling to verify the remediation
Caveat Major version upgrades (e.g., Jetty 9 to 10) may introduce API compatibility 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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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