# CVE-2023-49356: Memory corruption in n/a

> A stack buffer overflow in MP3Gain allows attackers to cause a denial of service via the WriteMP3GainAPETag function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2023
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2023-49356, GHSA-9vwc-6w53-v9f8

## What is CVE-2023-49356?

CVE-2023-49356 is a high-severity memory corruption vulnerability in n/a, published on 22 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack buffer overflow vulnerability in MP3Gain v1.6.2 allows an attacker to cause a denial of service via the WriteMP3GainAPETag function at apetag.c:592.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-49356?

It affects 1 product.


Products: Glensawyer Mp3gain.

## How do I fix CVE-2023-49356?

No fix published yet.

## Is CVE-2023-49356 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49356 exists.

## Other vulnerabilities in n/a

- [CVE-2021-34085](https://insights.sbomify.com/CVE-2021-34085/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-18359](https://insights.sbomify.com/CVE-2019-18359/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49356 and fix it if it is affected.

What it is: CVE-2023-49356 is a high-severity memory corruption vulnerability in n/a, published on 22 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49356 exists.

Affected product: n/a. 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-2023-49356/ (Markdown: https://insights.sbomify.com/CVE-2023-49356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49356
- OSV: https://osv.dev/vulnerability/CVE-2023-49356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-49356/
Summaries are generated and may contain mistakes; the official description above is the record.