Skip to content
Fencer Intel
medium 5.5

CVE-2017-11548 json

The _tokenize_matrix function in audio_out.c in Xiph.Org libao 1.2.0 allows remote attackers to cause a denial of service (memory corruptio…

published 2017-07-31 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3164

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.9%
EPSS 3.9% chance of exploitation in 30 days, percentile 90%
public exploits
1
Exploit-DB

Summary

The _tokenize_matrix function in audio_out.c in Xiph.Org libao 1.2.0 allows remote attackers to cause a denial of service (memory corruption) via a crafted MP3 file.

Patch / fix

  • libao Alpine 3.24, Alpine 3.23, Alpine 3.22 +14 more 1.2.0-r3
  • libao Alpine 3.7, Alpine 3.6, Alpine 3.5 1.2.0-r2

alpine advisories ALPINE-CVE-2017-11548

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-11548 updated cvss 3.3

libao: Invalid memory allocation in _tokenize_matrix function in audio_out.c

  • Red Hat Enterprise Linux 5 libao Red Hat Enterprise Linux 6 libao Red Hat Enterprise Linux 7 libao
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-42400)
  2. Published

Exploit prediction

3.85% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-42400 libao 1.2.0 - Denial of Service dos, 2017-07-31

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.