CVE-2026-57197: Asterisk: Heap Buffer Overflow in OGG/Speex File Playback (format_ogg_speex)
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, an unbounded memcpy of OGG/Speex packet data in formatoggspeex can cause a heap buffer overflow and crash Asterisk when reading a file containing corrupted Speex audio. The attacker must create the file and make it available to Asterisk either through sufficiently elevated privileges or by convincing an Asterisk administrator to make it available. Asterisk must also be configured to play that file. 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Asteriskto a version that resolves this vulnerability.Fixed in 20.20.1 - Upgrade
Upgrade
Asteriskto a version that resolves this vulnerability.Fixed in 21.12.3 - Upgrade
Upgrade
Asteriskto a version that resolves this vulnerability.Fixed in 22.10.1 - Upgrade
Upgrade
Asteriskto a version that resolves this vulnerability.Fixed in 23.4.1 - Upgrade
Upgrade
Certified Asteriskto a version that resolves this vulnerability.Fixed in 20.7-cert11 - Upgrade
Upgrade
Certified Asteriskto a version that resolves this vulnerability.Fixed in 22.8-cert3
Event History
Frequently Asked Questions
Who is exposed to this issue?
Asterisk and Certified Asterisk deployments are exposed if they run a version earlier than the listed fixed releases, have a corrupted OGG/Speex file available to the server, and are configured to play that file.
What does an attacker need to exploit it?
The attacker must create a corrupted Speex audio file and make it available to Asterisk. This requires sufficiently elevated privileges or persuading an Asterisk administrator to add the file, and Asterisk must subsequently play it.
Is a default installation affected simply by receiving a malformed audio file?
No. The malformed file must be made available to Asterisk and explicitly configured for playback; the issue is triggered while Asterisk reads that file.
What is the impact if exploitation succeeds?
The unbounded memcpy can overflow a heap buffer and crash Asterisk.
Which releases contain the fix?
The issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, and 23.4.1, and in Certified Asterisk 20.7-cert11 and 22.8-cert3.