jackson-dataformat-smile denial of service in raw-binary parsing
FasterXML jackson-dataformat-smile
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| FasterXML jackson-dataformat-smile |
|
|
| FasterXML jackson-dataformat-smile |
|
FasterXML jackson-dataformat-smile
| Product | Affected | Fixed in |
|---|---|---|
| FasterXML jackson-dataformat-smile |
|
|
| FasterXML jackson-dataformat-smile |
|
≥ 3.2.0 · < 3.2.4
|
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.
From the CVE record · HeroDevs
The asynchronous Smile parser allocates memory based on an untrusted raw-binary length without an upper bound or overflow check. An unauthenticated attacker who can submit Smile data for parsing can cause an approximately 2 GB allocation or a negative array length, crashing the request or processing thread. No user interaction is required.
Engineers running FasterXML jackson-dataformat-smile with the asynchronous Smile parser should check their deployments; affected versions were not provided.