CyberRota Analysis
AI-GeneratedApache's CompressionUtils.inflate() function is vulnerable to a denial-of-service attack due to the lack of an output-size cap when decompressing attacker-controlled DEFLATE data. This flaw allows a small crafted payload to expand significantly in memory, potentially leading to resource exhaustion. Organizations using affected versions of Apache should prioritize upgrading to versions 4.2.4, 4.1.9, or 3.6.13 to mitigate this risk.
Original NVD Description
CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with no output-size cap. A small (~KB) crafted payload could expand to gigabytes on the heap. Reachable via JWE decryption when zip=DEF (e.g. JoseSessionTokenProvider with RSA-OAEP key wrap) and via SAML redirect/POST binding token inflation — in both cases decompression happens before/independent of trust validation. Fix: Added a configurable maximum inflated-size cap (default 10 MiB, org.apache.cxf.compression-max-inflated-size system property) to CompressionUtils.inflate(); aborts with DataFormatException once exceeded. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Related CVEs
Other vulnerabilities affecting the same vendor(s)