You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2026/07/11 08:26:00 UTC
[jira] [Created] (AVRO-4276) [C++] BinaryDecoder::doDecodeItemCount() missing INT64_MIN rejection allows DoS via crafted block count
Ismaël Mejía created AVRO-4276:
----------------------------------
Summary: [C++] BinaryDecoder::doDecodeItemCount() missing INT64_MIN rejection allows DoS via crafted block count
Key: AVRO-4276
URL: https://issues.apache.org/jira/browse/AVRO-4276
Project: Apache Avro
Issue Type: Bug
Components: c++
Reporter: Ismaël Mejía
BinaryDecoder::doDecodeItemCount() in lang/c++/impl/BinaryDecoder.cc does not reject INT64_MIN as a block count. While the -(result + 1) + 1 idiom (added in AVRO-4228) avoids undefined behavior, it silently converts INT64_MIN to 2^63 as the item count. Callers such as Generic.cc then attempt vector::resize(2^63), triggering std::bad_alloc and crashing the process.
An attacker can craft a 10-byte varint (FF FF FF FF FF FF FF FF FF 01, zigzag encoding of INT64_MIN) as an array or map block count to trigger this denial of service.
The C binding already rejects INT64_MIN explicitly (AVRO-4275). The C++ binding should do the same.
Fix: Guard against INT64_MIN before negation in doDecodeItemCount(), and simplify the negation to -result (safe once INT64_MIN is excluded).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)