# CVE-2022-24599: Information disclosure in n/a

> An attacker can leak sensitive information via a crafted file due to a memory leak in the Audio File Library's printfileinfo function.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Feb 2022
- **Updated:** 3 Nov 2025
- **Also known as:** AZL-66560, AZL-66563, DEBIAN-CVE-2022-24599, GHSA-9hgh-v7v7-5f66, MGASA-2023-0336, UBUNTU-CVE-2022-24599, openSUSE-SU-2025:15050-1

## What is CVE-2022-24599?

CVE-2022-24599 is a medium-severity vulnerability in Debian Debian Linux, published on 22 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In autofile Audio File Library 0.3.6, there exists one memory leak vulnerability in printfileinfo, in printinfo.c, which allows an attacker to leak sensitive information via a crafted file. The printfileinfo function calls the copyrightstring function to get data, however, it dosn't use zero bytes to truncate the data.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `audiofile` | openSUSE:Tumbleweed | All versions | 0.3.6-15.1 |

Products: Audiofile Audiofile, Debian Debian Linux, Fedoraproject Fedora.

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

Apply the vendor's patch.

## Is CVE-2022-24599 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-7747](https://insights.sbomify.com/CVE-2015-7747/): Memory corruption in n/a (high 8.8)
- [CVE-2018-17095](https://insights.sbomify.com/CVE-2018-17095/): Memory corruption in n/a (high 8.8)
- [CVE-2017-6827](https://insights.sbomify.com/CVE-2017-6827/): Memory corruption in n/a (high 7.8)
- [CVE-2017-6828](https://insights.sbomify.com/CVE-2017-6828/): Memory corruption in n/a (high 7.8)
- [CVE-2025-50950](https://insights.sbomify.com/CVE-2025-50950/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24599 is a medium-severity vulnerability in Debian Debian Linux, published on 22 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-24599 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-24599/ (Markdown: https://insights.sbomify.com/CVE-2022-24599/index.md)
```

## Sources

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

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