# CVE-2020-22617: Use after free in n/a

> A use-after-free vulnerability in Ardour's XML processing allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 8 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-22617, GHSA-595v-6p68-9v59, UBUNTU-CVE-2020-22617, USN-5110-1

## What is CVE-2020-22617?

CVE-2020-22617 is a critical use after free vulnerability in n/a, published on 8 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ardour v5.12 contains a use-after-free vulnerability in the component ardour/libs/pbd/xml++.cc when using xmlFreeDoc and xmlXPathFreeContext.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Ardour Ardour.

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

Apply the vendor's patch.

## Is CVE-2020-22617 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3349](https://insights.sbomify.com/CVE-2010-3349/): Path traversal in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-22617 is a critical use after free vulnerability in n/a, published on 8 Oct 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-2020-22617 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-2020-22617/ (Markdown: https://insights.sbomify.com/CVE-2020-22617/index.md)
```

## Sources

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

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