An out-of-bounds read issue was discovered in the Yubico-Piv 1.5.0 smartcard driver.
An out-of-bounds read issue was discovered in the Yubico-Piv 1.5.0 smartcard driver. The file lib/ykpiv.c contains the following code in the function `_ykpiv_fetch_object()`: {% highlight c %} if(sw == SW_SUCCESS) { size_t outlen; int offs = _ykpiv_get_length(data + 1, &outlen); if(offs == 0) { return YKPIV_SIZE_ERROR; } memmove(data, data + 1 + offs, outlen); *len = outlen; return YKPIV_OK; } else { return YKPIV_GENERIC_ERROR; } {% endhighlight %} -- in the end, a `memmove()` occurs with a length retrieved from APDU data. This length is not checked for whether it is outside of the APDU data retrieved. Therefore the `memmove()` could copy bytes behind the allocated data buffer into this buffer.
- Published
- Aug 15, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-125
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| yubico | piv manager | cpe:2.3:a:yubico:piv_manager |
| yubico | piv tool | cpe:2.3:a:yubico:piv_tool |
| yubico | smart card minidriver | cpe:2.3:a:yubico:smart_card_minidriver |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- yubico piv managerbefore 1.4.2
- yubico piv manager1.4.2
- yubico piv manager1.4.2b
- yubico piv manager1.4.2c
- yubico piv manager1.4.2d
- yubico piv manager1.4.2e
- yubico piv manager1.4.2f
- yubico piv manager1.4.2g
- yubico piv toolbefore 1.6.0
- yubico smart card minidriverup to 3.7.3.160 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | yubico-piv-tool | before 1.6.1-1 | 1.6.1-1 |
| openSUSE:Leap 15.0 | yubico-piv-tool | before 1.5.0-lp150.2.3.1 | 1.5.0-lp150.2.3.1 |
| openSUSE:Tumbleweed | yubico-piv-tool | before 2.2.0-1.5 | 2.2.0-1.5 |
| SUSE:Linux Enterprise Module for Basesystem 15 | yubico-piv-tool | before 1.5.0-3.3.33 | 1.5.0-3.3.33 |
Same product
yubico: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-14779A buffer overflow issue was discovered in the Yubico-Piv 1.5.0 smartcard driver.27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:yubico-piv-tool | 1.6.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:yubico-piv-tool | 1.5.0-lp150.2.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:yubico-piv-tool | 1.5.0-3.3.33 · SUSE:Linux Enterprise Module for Basesystem 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.openwall.com/lists/oss-security/2018/08/14/2
- usn.ubuntu.com/4276-1/
- www.x41-dsec.de/lab/advisories/x41-2018-001-Yubico-Piv/
- www.yubico.com/support/security-advisories/ysa-2018-03/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.