# CVE-2021-34185: Integer overflow in n/a

> An integer overflow in the miniaudio library allows attackers to cause buffer overflows, potentially leading to code execution or crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4pm9-37wq-m3h9

## What is CVE-2021-34185?

CVE-2021-34185 is a high-severity vulnerability in n/a, published on 25 Jun 2021. 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

Miniaudio 0.10.35 has an integer-based buffer overflow caused by an out-of-bounds left shift in drwav_bytes_to_u32 in miniaudio.h

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Mackron Miniaudio.

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

No fix has been published for CVE-2021-34185 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-34185 being exploited?

There is no known exploitation of CVE-2021-34185 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-34184](https://insights.sbomify.com/CVE-2021-34184/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-41147](https://insights.sbomify.com/CVE-2024-41147/): Memory corruption in Miniaudio (high 7.7)
- [CVE-2026-32837](https://insights.sbomify.com/CVE-2026-32837/): mackron / miniaudio Out-of-Bounds Read in BEXT Coding History Parsing (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-34185 is a high-severity vulnerability in n/a, published on 25 Jun 2021. 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-2021-34185 in the wild and no public exploit code.

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-34185/ (Markdown: https://insights.sbomify.com/CVE-2021-34185/index.md)
```

## Sources

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

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