CVE-2022-2191: Jetty SslConnection does not release pooled ByteBuffers in case of errors
7.5
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.63522%
CWE
Published
7/7/2022
Updated
1/28/2023
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| org.eclipse.jetty:jetty-server | maven | >= 11.0.0, < 11.0.10 | 11.0.10 |
| org.eclipse.jetty:jetty-server | maven | >= 10.0.0, < 10.0.10 | 10.0.10 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from SslConnection's failure to release pooled ByteBuffers during error handling. The core issue occurs in SSL processing paths where:
- Buffers are acquired from RetainableByteBufferPool
- Error conditions (like TLS handshake failures) occur
- Buffers are not properly released back to the pool
While exact line numbers aren't available, the advisory specifically implicates SslConnection error paths. The DecryptedEndPoint's fill() and flush() methods are critical SSL processing points where buffer acquisition occurs. The vulnerability pattern matches common SSL handler implementations where buffer release might be missed in exception handling blocks. The high confidence comes from the direct correlation between the vulnerability description and these core SSL processing methods in Jetty's architecture.