Live › vulnerability › CVE-2026-57201
Go to dashboardA stack buffer overflow in Asterisk's H.323 ooTrace() logging function, reached through the chan_ooh323 channel driver, can be triggered by a crafted packet. The result described in the sources is a crash of the Asterisk process, denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 17:32 UTC. All times on this page are UTC.
Only systems that have chan_ooh323 explicitly compiled and installed, which is not the default, and whose H.323 port is publicly reachable. Deployments without the addon driver or with the port restricted to trusted networks are not exposed.
No product ranges from the sources yet.
ls /usr/lib/asterisk/modules/ | grep ooh323 (path may vary by install)asterisk -rx "core show version"20.20.1, 21.12.3, 22.10.1 or 23.4.1, or Certified Asterisk 20.7-cert11 or 22.8-cert3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Asterisk is an open source private branch exchange and telephony toolkit. Prior to Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3, a stack buffer overflow in the H.323 ooTrace() trace-logging function can occur when unbounded vsprintf writes into a fixed 2048-byte buffer. A remote attacker may send a carefully crafted packet that causes the Asterisk process to crash. The chan_ooh323 addon channel driver must be explicitly compiled and installed, which is not the default, and its port must be publicly reachable. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.
This page as .md · .json · in your agent: get_signal("CVE-2026-57201")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.