jackson-dataformat-smile: unbounded eager byte[] allocation for raw binary in the async parser allows OutOfMemoryError denial of service
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.18.12, 2.21.8, 2.22.4, 3.1.8, 3.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The jackson-dataformat-smile library, specifically its asynchronous (non-blocking) Smile parser, is affected. An attacker who can submit Smile-encoded data for parsing can send a tiny message that makes the parser allocate a very large byte array, causing an OutOfMemoryError or an unchecked NegativeArraySizeException that can crash the request or processing thread and cause a denial of service.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The asynchronous Smile parser (NonBlockingByteArrayParser) uses a raw-binary length prefix taken from untrusted input to allocate a byte[] before the body is read, with no upper bound and no overflow check. On the raw-binary marker 0xFD, _decodeVInt() computes (value << 6) + (i & 0x3F) without the (value >>> 25) != 0 overflow guard present in the blocking SmileParser._readUnsignedVInt, and _startRawBinary then allocates the declared length immediately. A Smile feed of roughly ten bytes can therefore force an eager allocation of approximately 2 GB, producing an OutOfMemoryError on reactive or asynchronous Smile endpoints. A VInt crafted to overflow int yields a negative length and a NegativeArraySizeException, a RuntimeException that is not a JacksonException and so escapes the parser contract. Either outcome crashes the request or processing thread. This is the same class of issue as CVE-2020-28491 in the CBOR parser of this library, which was fixed with a LONGEST_NON_CHUNKED_BINARY guard; the asynchronous Smile parser never received the equivalent guard. No privileges or user interaction beyond the ability to submit data for parsing are required.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- com.fasterxml.jackson.dataformat:jackson-dataformat-smile
From 2.9.0 · fixed in 2.18.12; From 2.19.0 · fixed in 2.21.8; From 2.22.0 · fixed in 2.22.4
- tools.jackson.dataformat:jackson-dataformat-smile
From 3.0.0 · fixed in 3.1.8; From 3.2.0 · fixed in 3.2.4