CVE-2019-14247 json
The scan() function in mad.c in mpg321 0.3.2 allows remote attackers to trigger an out-of-bounds write via a zero bitrate in an MP3 file.
published 2019-07-24 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-5487
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
The scan() function in mad.c in mpg321 0.3.2 allows remote attackers to trigger an out-of-bounds write via a zero bitrate in an MP3 file.
Patch / fix
- mpg321 Debian 14, Debian 13, Debian 12 0.3.2-2
debian advisories DEBIAN-CVE-2019-14247
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-2019-14247 updated cvss 5.5
mpg321: out-of-bounds write via a zero bitrate in an MP3 file
-
Red Hat Enterprise Linux 7 mpg123, mpg123-libs, mpg123-plugins-pulseaudio Red Hat Enterprise Linux 8 mpg123, mpg123-libs, mpg123-plugins-pulseaudionot affected: vulnerable code not present
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
Exploit prediction
1.38% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- sourceforge.net https://sourceforge.net/p/mpg321/bugs/51/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/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-787 Out-of-bounds Write
References
-
sourceforge.net
/p/mpg321/bugs/51/
exploit, third-party-advisory
Sources
- CVE List CVE-2019-14247
- NVD CVE-2019-14247
Fencer Vulns 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.