# CVE-2020-15710: Potential double-free in pulseaudio

> A local attacker can trigger a double-free in PulseAudio's Bluetooth module, causing a crash or memory leak.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Nov 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-87cm-47xv-j472, UBUNTU-CVE-2020-15710, USN-4519-1

## What is CVE-2020-15710?

CVE-2020-15710 is a medium-severity use after free vulnerability in Canonical PulseAudio, published on 19 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Potential double free in Bluez 5 module of PulseAudio could allow a local attacker to leak memory or crash the program. The modargs variable may be freed twice in the fail condition in src/modules/bluetooth/module-bluez5-device.c and src/modules/bluetooth/module-bluez5-device.c. Fixed in 1:8.0-0ubuntu3.14.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2020-15710?

It affects 1 product.


Products: Pulseaudio Project Pulseaudio.

## How do I fix CVE-2020-15710?

Apply the vendor's patch.

## Is CVE-2020-15710 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15710 and fix it if it is affected.

What it is: CVE-2020-15710 is a medium-severity use after free vulnerability in Canonical PulseAudio, published on 19 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-15710 in the wild and no public exploit code.

Affected product: Canonical PulseAudio. 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-2020-15710/ (Markdown: https://insights.sbomify.com/CVE-2020-15710/index.md)
```

## Sources

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

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