# CVE-2021-39282: Denial of service in n/a

> A memory leak in the AC3AudioStreamParser allows attackers to cause a denial of service by processing malicious AC3 files.

- **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:** 18 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-39282, GHSA-3x73-wm98-jh2g, UBUNTU-CVE-2021-39282

## What is CVE-2021-39282?

CVE-2021-39282 is a high-severity denial of service vulnerability in n/a, published on 18 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Live555 through 1.08 has a memory leak in AC3AudioStreamParser for AC3 files.

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

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

It affects 1 product.


Products: Live555 Live555.

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

Upgrade to a fixed version.

## Is CVE-2021-39282 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-37117](https://insights.sbomify.com/CVE-2023-37117/): Use after free in n/a (critical 9.8)
- [CVE-2021-41396](https://insights.sbomify.com/CVE-2021-41396/): Memory corruption in n/a (high 7.5)
- [CVE-2021-38380](https://insights.sbomify.com/CVE-2021-38380/): Denial of service in n/a (high 7.5)
- [CVE-2021-38381](https://insights.sbomify.com/CVE-2021-38381/): Use after free in n/a (medium 6.5)
- [CVE-2021-38382](https://insights.sbomify.com/CVE-2021-38382/): Use after free in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-39282 is a high-severity denial of service vulnerability in n/a, published on 18 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-39282 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-39282/ (Markdown: https://insights.sbomify.com/CVE-2021-39282/index.md)
```

## Sources

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

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