# CVE-2022-46449: Memory corruption in n/a

> Attackers can cause a Denial of Service in MPD via crafted input due to a memory corruption vulnerability.

- **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:** 10 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-7p75-2vwp-g822, UBUNTU-CVE-2022-46449, openSUSE-SU-2024:12618-1

## What is CVE-2022-46449?

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

### Official description

An issue in MPD (Music Player Daemon) v0.23.10 allows attackers to cause a Denial of Service (DoS) via a crafted input.

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

## Which versions are affected by CVE-2022-46449?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mpd` | openSUSE:Tumbleweed | All versions | 0.23.12-1.1 |

Products: Musicpd Music Player Daemon.

## How do I fix CVE-2022-46449?

Apply the vendor's patch.

## Is CVE-2022-46449 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-48363](https://insights.sbomify.com/CVE-2022-48363/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46449 and fix it if it is affected.

What it is: CVE-2022-46449 is a high-severity memory corruption vulnerability in n/a, published on 10 Jan 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-2022-46449 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-2022-46449/ (Markdown: https://insights.sbomify.com/CVE-2022-46449/index.md)
```

## Sources

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

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