Skip to content
Fencer Vulns
medium 4.3

CVE-2020-13132 json

An issue was discovered in Yubico libykpiv before 2.1.0.

published 2020-07-09 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-5408

cvss
4.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

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.

Patch / fix

  • yubico libykpiv 2.1.0
  • yubico piv_tool_manager 2.0.0
  • yubico-piv-tool Debian 14, Debian 13, Debian 12 2.1.1-1

debian advisories DEBIAN-CVE-2020-13132

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-13132 updated cvss 4.6

yubico-piv-tool: incorrect free() in the ykpiv_util_generate_key() in lib/util.c through incorrect error handling code could result in DoS

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • blog.inhq.net https://blog.inhq.net/posts/yubico-libykpiv-vuln/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 4.3 CVSS:3.0/AC:L/AV:P/A:H/C:N/I:N/PR:N/S:U/UI:R
NVD 3.1 4.6 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.0 4.3 CVSS:3.0/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-763 Release of Invalid Pointer or Reference

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.