| Title | tdunning t-digest 3.2 Unvalidated Length Fields Enable Crash |
|---|
| Description | I was auditing t-digest 3.2's binary deserialization path for spots where untrusted bytes land directly on an array index or allocation size. MergingDigest.fromBytes(ByteBuffer) reads four attacker-controlled numeric fields (compression, n, bufferSize, lastUsedCell) straight off the wire and uses every one of them without a bounds check, so a handful of crafted bytes is enough to throw NegativeArraySizeException or ArrayIndexOutOfBoundsException before a single real centroid gets parsed. I confirmed the same unvalidated code is still on master today, and found a real consumer — Apache Pinot's star-tree aggregator — that fed this exact method with raw ingested byte[] values with no validation of its own until a July 2026 hardening PR. |
|---|
| Source | ⚠️ https://github.com/tdunning/t-digest/issues/227 |
|---|
| User | Yu Bao from PayPal Cyber Security Team (UID 99838) |
|---|
| Submission | 08/14/2026 03:36 (1 month ago) |
|---|
| Moderation | 09/14/2026 09:11 (1 month later) |
|---|
| Status | Duplicate |
|---|
| VulDB entry | 402019 [tdunning t-digest up to 3.3 Serialization MergingDigest.fromBytes capacity memory corruption] |
|---|
| Points | 0 |
|---|