CVE 8.8 HIGH

Stack buffer overflow in SCTP error cause parsing in inet_drv allows remote VM crash_CVE-2026-49759

8.8 / 10
HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Description

Stack-based Buffer Overflow vulnerability in Erlang OTP erts (inet_drv) allows an unauthenticated remote attacker to crash the BEAM VM by sending a crafted SCTP ERROR chunk.

The sctp_parse_error_chunk function in erts/emulator/drivers/common/inet_drv.c parses SCTP ERROR chunks and writes cause codes into a fixed-size stack-allocated ErlDrvTermData spec[] array without checking bounds. A remote attacker who has established an SCTP association to a listening port can send a single crafted SCTP ERROR chunk containing enough cause codes to overflow the stack buffer, crashing the VM. The attacker can only write 16-bit values interleaved with a fixed tag, so the overflow does not provide a controlled return address, limiting exploitation to Denial of Service.

A crafted SCTP ERROR chunk may also leak bits and pieces of Erlang VM memory into the received error packet observed by the Erlang process. Such data is already readable by the user running the Erlang VM, so the disclosure scope is limited.

This issue affects OTP from OTP 17.0 before 27.3.4.13, 28.5.0.2 and 29.0.2, corresponding to erts from 6.0 before 15.2.7.9, 16.4.0.2 and 17.0.2.

AI Analysis

Stack-based Buffer Overflow vulnerability in Erlang OTP erts (inet_drv) allowing remote VM crash via crafted SCTP ERROR chunk

Basic Information

ID CVE-2026-49759
Source EEF
Published Jun 10, 2026 at 14:35
Modified Jun 10, 2026 at 16:18

Affected Product

Vendor Erlang
Product OTP
Version 6.0
Affected Versions Erlang OTP 6.0
Erlang OTP 17.0
Erlang OTP 84adefa331c4159d432d22840663c38f155cd4c1

CWE Classification

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor Erlang
Product Erlang OTP
Version 6.0 before 15.2.7.9, 16.4.0.2, 17.0.2

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.