# CVE-2024-10573: Mpg123: buffer overflow when writing decoded pcm samples > An out-of-bounds write in libmpg123 allows arbitrary code execution via crafted streams, requiring user interaction to scan the stream. - **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 31 Oct 2024 - **Updated:** 20 Nov 2025 - **Also known as:** ALPINE-CVE-2024-10573, ALSA-2024:11193, ALSA-2024:11242, CLSA-2026-1779694248, DEBIAN-CVE-2024-10573, DLA-3967-1, DSA-5811-1, GHSA-7m7j-pgpw-9g75, MGASA-2024-0358, RHSA-2024:11193, RHSA-2024:11242, RLSA-2024:11193, RLSA-2024:11242, UBUNTU-CVE-2024-10573, USN-7092-1, USN-7092-2, openSUSE-SU-2024:14454-1 ## What is CVE-2024-10573? CVE-2024-10573 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 7, published on 31 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description An out-of-bounds write flaw was found in mpg123 when handling crafted streams. When decoding PCM, the libmpg123 may write past the end of a heap-located buffer. Consequently, heap corruption may happen, and arbitrary code execution is not discarded. The complexity required to exploit this flaw is considered high as the payload must be validated by the MPEG decoder and the PCM synth before execution. Additionally, to successfully execute the attack, the user must scan through the stream, making web live stream content (such as web radios) a very unlikely attack vector. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2024-10573? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mpg123` | AlmaLinux:8 | All versions | 1.32.9-1.el8_10 | | `mpg123-devel` | AlmaLinux:8 | All versions | 1.32.9-1.el8_10 | | `mpg123-libs` | AlmaLinux:8 | All versions | 1.32.9-1.el8_10 | | `mpg123-plugins-pulseaudio` | AlmaLinux:8 | All versions | 1.32.9-1.el8_10 | | `mpg123` | AlmaLinux:9 | All versions | 1.32.9-1.el9_5 | | `mpg123-devel` | AlmaLinux:9 | All versions | 1.32.9-1.el9_5 | | `mpg123-libs` | AlmaLinux:9 | All versions | 1.32.9-1.el9_5 | | `mpg123-plugins-pulseaudio` | AlmaLinux:9 | All versions | 1.32.9-1.el9_5 | | `mpg123` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-plugins-pulseaudio` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-plugins-pulseaudio-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.32.9-1.el8_10 | | `mpg123-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.32.9-1.el8_10 | | `mpg123-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.32.9-1.el8_10 | | `mpg123-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.32.9-1.el8_10 | | `mpg123-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.32.9-1.el8_10 | | `mpg123-plugins-pulseaudio-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:1.32.9-1.el8_10 | | `mpg123` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-plugins-pulseaudio` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-plugins-pulseaudio-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.32.9-1.el9_5 | | `mpg123-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.32.9-1.el9_5 | | `mpg123-debugsource` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.32.9-1.el9_5 | | `mpg123-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.32.9-1.el9_5 | | `mpg123-libs-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.32.9-1.el9_5 | | `mpg123-plugins-pulseaudio-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:1.32.9-1.el9_5 | | `mpg123` | Rocky Linux:8 | All versions | 0:1.32.9-1.el8_10 | | `mpg123` | Rocky Linux:9 | All versions | 0:1.32.9-1.el9_5 | | `mpg123` | openSUSE:Tumbleweed | All versions | 1.32.9-1.1 | ## How do I fix CVE-2024-10573? Apply the vendor's patch. ## Is CVE-2024-10573 being exploited? There is no known exploitation of CVE-2024-10573 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-10573 and fix it if it is affected. What it is: CVE-2024-10573 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 7, published on 31 Oct 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-10573 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 7. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-10573/ (Markdown: https://insights.sbomify.com/CVE-2024-10573/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10573 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10573 - OSV: https://osv.dev/vulnerability/CVE-2024-10573 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-10573/ Summaries are generated and may contain mistakes; the official description above is the record.