# CVE-2021-32419: Memory corruption in n/a

> An attacker can exploit a memory corruption flaw in Schism Tracker to read sensitive information or potentially execute code via a malicious file.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** DEBIAN-CVE-2021-32419, GHSA-23ph-fhq5-g5v8, UBUNTU-CVE-2021-32419

## What is CVE-2021-32419?

CVE-2021-32419 is a medium-severity memory corruption vulnerability in n/a, published on 17 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Schism Tracker v20200412 fixed in v.20200412 allows attacker to obtain sensitive information via the fmt_mtm_load_song function in fmt/mtm.c.

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

## Which versions are affected by CVE-2021-32419?

It affects 1 product.


Products: Schismtracker Schism Tracker.

## How do I fix CVE-2021-32419?

Upgrade to a fixed version.

## Is CVE-2021-32419 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14523](https://insights.sbomify.com/CVE-2019-14523/): Integer overflow in n/a (high 7.8)
- [CVE-2019-14465](https://insights.sbomify.com/CVE-2019-14465/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32419 and fix it if it is affected.

What it is: CVE-2021-32419 is a medium-severity memory corruption vulnerability in n/a, published on 17 Feb 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-2021-32419 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-2021-32419/ (Markdown: https://insights.sbomify.com/CVE-2021-32419/index.md)
```

## Sources

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

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