Heap pointer corruption via signed/unsigned mismatch in LARGE_TUPLE_EXT decoding in erts external term format decoder
Erlang OTP
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Erlang OTP |
| No fix yet |
| Erlang OTP |
| No fix yet |
| Erlang OTP |
| No fix yet |
Erlang OTP
| Product | Affected | Fixed in |
|---|---|---|
| Erlang OTP |
| No fix yet |
| Erlang OTP |
| No fix yet |
| Erlang OTP |
| No fix yet |
Signed to Unsigned Conversion Error and Out-of-bounds Write vulnerability in Erlang OTP erts allows an attacker who can supply a crafted Erlang external term format (ETF) binary to binary_to_term/1 to corrupt the BEAM heap pointer and crash the virtual machine.
When decoding a LARGE_TUPLE_EXT term, the validation pass decoded_size() in erts/emulator/beam/external.c reads the 32-bit arity field as unsigned (get_uint32()), while the decode pass dec_term() reads the same field as a signed 32-bit integer (get_int32()) into an int. An arity wire value of 0x80000000 passes validation as 2147483648 but decodes as -2147483648, so the subsequent hp += n moves the heap allocation pointer backward. Neither pass enforces the runtime tuple-arity limit MAX_ARITYVAL. The result is an out-of-bounds heap write; in practice the VM detects an impossible heap size and aborts, denying service. The required padding is large when uncompressed but the compressed-ETF envelope shrinks it to a small payload on the wire.
This issue affects OTP from OTP 25.0 before OTP 27.3.4.15, OTP 28.5.0.4, and OTP 29.0.4, corresponding to erts from 13.0 before 15.2.7.11, 16.4.0.4, and 17.0.4.
From the CVE record · EEF
Erlang OTP's erts component handles a tuple-arity value inconsistently when decoding Erlang external term format (ETF) data. An attacker who can supply a crafted ETF binary to binary_to_term/1 can cause an out-of-bounds heap write that, in practice, crashes the virtual machine. The input does not specify whether network access, authentication, or user interaction is required.
Engineers running Erlang OTP from OTP 25.0 before the applicable fixes in OTP 27.3.4.15, 28.5.0.4, or 29.0.4 should check their deployments.