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

> An attacker can trigger a denial of service in the Yubico libykpiv library via incorrect error handling leading to an invalid free operation.

- **Severity:** Medium 4.3 (`CVSS:3.0/AC:L/AV:P/A:H/C:N/I:N/PR:N/S:U/UI:R`)
- **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:** 9 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-13132, GHSA-mg7w-vxv4-393q, UBUNTU-CVE-2020-13132

## What is CVE-2020-13132?

CVE-2020-13132 is a medium-severity use after free vulnerability in n/a, published on 9 Jul 2020. 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 issue was discovered in Yubico libykpiv before 2.1.0. An attacker can trigger an incorrect free() in the ykpiv_util_generate_key() function in lib/util.c through incorrect error handling code. This could be used to cause a denial of service attack.

Weakness: CWE-763 (Release of Invalid Pointer or Reference)

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

It affects 3 products.


Products: Yubico Libykpiv, Yubico Piv Tool Manager, Yubico Yubikey Smart Card Minidriver.

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

Upgrade to a fixed version.

## Is CVE-2020-13132 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-13131](https://insights.sbomify.com/CVE-2020-13131/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13132 is a medium-severity use after free vulnerability in n/a, published on 9 Jul 2020. 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: There is no known exploitation of CVE-2020-13132 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-13132/ (Markdown: https://insights.sbomify.com/CVE-2020-13132/index.md)
```

## Sources

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

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