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

> An off-by-one error in Libsndfile allows attackers to execute arbitrary code or cause denial of service via crafted WAV files.

- **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:** Yes
- **Published:** 18 Jul 2023
- **Updated:** 28 Oct 2024
- **Also known as:** AZL-28506, AZL-34939, GHSA-6g97-p9mv-cpgv, ROOT-OS-DEBIAN-12-CVE-2022-33064

## What is CVE-2022-33064?

CVE-2022-33064 is a high-severity memory corruption vulnerability in n/a, published on 18 Jul 2023. 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 off-by-one error in function wav_read_header in src/wav.c in Libsndfile 1.1.0, results in a write out of bound, which allows an attacker to execute arbitrary code, Denial of Service or other unspecified impacts.

Weakness: CWE-193 (Off-by-one Error)

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

It affects 1 product.


Products: Libsndfile Project Libsndfile.

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

Upgrade to a fixed version.

## Is CVE-2022-33064 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6892](https://insights.sbomify.com/CVE-2017-6892/): Memory corruption in libsndfile (high 8.8)
- [CVE-2022-33065](https://insights.sbomify.com/CVE-2022-33065/): Integer overflow in n/a (high 7.8)
- [CVE-2026-37555](https://insights.sbomify.com/CVE-2026-37555/): Integer overflow in n/a (high 7.5)
- [CVE-2025-52194](https://insights.sbomify.com/CVE-2025-52194/): Memory corruption in n/a (high 7.5)
- [CVE-2024-50613](https://insights.sbomify.com/CVE-2024-50613/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33064 is a high-severity memory corruption vulnerability in n/a, published on 18 Jul 2023. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-33064 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-33064/ (Markdown: https://insights.sbomify.com/CVE-2022-33064/index.md)
```

## Sources

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

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