CyberRota Analysis
AI-GeneratedThe AsyncHttpClient library in Java versions 2.0.0 to 2.16.1 and 3.0.8 to 3.0.10 is vulnerable to an OutOfMemoryError due to unbounded automatic response decompression, allowing attackers to exploit this flaw by sending specially crafted responses that can exhaust the client's heap memory. This vulnerability poses a significant risk to applications relying on AHC for HTTP requests, particularly in environments where untrusted servers are accessed. Organizations using affected versions should prioritize upgrading to versions 2.16.1 or 3.0.12 to mitigate this high-severity risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 2.0.0 until 2.16.1 and 3.0.12, automatic response decompression on the HTTP/1.1 path uses ChannelManager.newHttpContentDecompressor() to install Http1ContentDecompressor without a cumulative output-size limit. A hostile or compromised server, or an attacker who can alter a response in transit, can send a small gzip, deflate, or snappy response that expands across chunks until the client exhausts its heap and raises OutOfMemoryError; brotli and zstd are also affected when their optional codecs are present. In versions 3.0.8 through 3.0.10, the HTTP/2 decompressor is also unbounded, so switching protocols does not mitigate the issue on those releases. A limit applied to each decode call is insufficient because the response can be delivered as many small chunks, so the fixed implementation tracks total decompressed bytes for the whole response. This issue is fixed in versions 2.16.1 and 3.0.12.