Jetty SslConnection does not release pooled ByteBuffers in case of errors

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-2191: 2.18% estimated exploitation activity in the next 30 days; percentile 82.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact SslConnection does not release ByteBuffers in case of error code paths. For example, TLS handshakes that require client-auth with clients that send expired certificates will trigger a TLS handshake errors and the ByteBuffers used to process the TLS handshake will be leaked. Workarounds Configure explicitly a RetainableByteBufferPool with max[Heap|Direct]Memory to limit the amount of memory that is leaked. Eventually the pool will be full of "active" entries (the leaked ones) and will provide ByteBuffers that will be GCed normally. With embedded-jetty With jetty-home/jetty-base Create a ${jetty.base}/etc/retainable-byte-buffer-config.xml And then reference it in ${jetty.base}/start.d/retainable-byte-buffer-config.ini References https://github.com/eclipse/jetty.project/issues/8161 For more information Email us at security@webtide.com

Published by the source

7 Jul 2022, 20:55 UTC

Last modified by the source

28 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 16:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8mpp-f3f7-xc28

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-2191

Advisory: Jetty SslConnection does not release pooled ByteBuffers in case of errors
IDs: CVE-2022-2191, GHSA-8mpp-f3f7-xc28
Record: https://patchnext.com/advisories/cve-2022-2191 (revision 1, source checked 26 Oct 2026, 16:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jetty:jetty-server 11.0.10, 10.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jetty:jetty-server: affected >= 11.0.0, < 11.0.10; >= 10.0.0, < 10.0.10; fixed in 11.0.10, 10.0.10

## Suggested inspection (read-only)
- Maven org.eclipse.jetty:jetty-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jetty:jetty-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8mpp-f3f7-xc28 (GitHub-reviewed advisory GHSA-8mpp-f3f7-xc28 lists affected ranges: Maven org.eclipse.jetty:jetty-server >=11.0.0 =10.0.0 <10.0.10)

Commands are suggestions: review each one before running it.