Security readout for executives and security teams
Plain-English summary
This issue affects Yubico ykneo-openpgp versions before 1.0.10. On first power-up, the device could issue a signature even though the PIN was not actually validated. Business risk depends on whether affected OpenPGP applets are used for signing workflows that rely on PIN enforcement.
Executive priority
Prioritize this where hardware-backed OpenPGP signatures protect sensitive code, legal, identity, or administrative workflows. Otherwise, handle as a targeted legacy-device remediation item.
Technical view
The CVE describes a PIN-validation logic error in ykneo-openpgp before 1.0.10. A signature may be generated after initial power-up despite an invalid PIN state. Public data in the bundle does not include CVSS, CWE, CPEs, or confirmed exploit activity.
Likely exposure
Exposure is likely limited to environments using Yubico ykneo-openpgp before version 1.0.10 for OpenPGP signing. The provided CVE data does not identify broader affected products or CPEs.
Exploitation context
The source bundle does not show active exploitation, and CISA KEV status is false. The described impact is unauthorized or unintended signing when PIN validation has not succeeded after power-up.
Researcher notes
Evidence is narrow but specific: a typo allowed signing after first power-up without valid PIN validation. Missing data includes CVSS, CWE classification, CPE mapping, exploit reports, and detailed remediation notes beyond the version boundary.
Mitigation direction
- Identify any ykneo-openpgp deployments before version 1.0.10.
- Update affected ykneo-openpgp installations to 1.0.10 or later where applicable.
- Review Yubico's advisory for vendor-specific handling guidance.
- Treat affected signing keys as higher risk until validated or remediated.
Validation and detection
- Inventory OpenPGP applet versions used in signing workflows.
- Confirm no deployed ykneo-openpgp version is earlier than 1.0.10.
- Review signing controls that assume PIN validation always precedes signature creation.
- Check vendor advisory details before accepting residual risk.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2015-3298 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://developers.yubico.com/ykneo-openpgp/SecurityAdvisory%202015-04-14.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.