Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2019-12210: In Yubico pam-u2f 1.0.7, when configured with debug and a custom debug log file is set using debug_file, that file descriptor is not closed

Noroxi assessment

Priority: Monitor (action score 33/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81.3% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: pam-u2f (Debian:12) 1.0.8-1; libu2f-host (openSUSE:Leap 15.0) 1.1.6-lp150.10.1; pam_u2f (openSUSE:Leap 15.0) 1.0.8-lp150.7.1.

Low priority for now. Upgrade to pam-u2f (Debian:12) 1.0.8-1; libu2f-host (openSUSE:Leap 15.0) 1.1.6-lp150.10.1; pam_u2f (openSUSE:Leap 15.0) 1.0.8-lp150.7.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Yubico pam-u2f 1.0.7, when configured with debug and a custom debug log file is set using debug_file, that file descriptor is not closed when a new process is spawned. This leads to the file descriptor being inherited into the child process; the child process can then read from and write to it. This can leak sensitive information and also, if written to, be used to fill the disk or plant misinformation.

HighCVSS 8.1 · v3.0—No exploit Fix available
Published
Jun 4, 2019
Updated
Jun 16, 2026
EPSS
2.0% · 81th percentile
CWE
—

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.0%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-12210

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for yubico records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
yubicopam-u2f

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • yubico pam-u2f1.0.7

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12pam-u2fbefore 1.0.8-11.0.8-1
openSUSE:Leap 15.0libu2f-hostbefore 1.1.6-lp150.10.11.1.6-lp150.10.1
openSUSE:Leap 15.0pam_u2fbefore 1.0.8-lp150.7.11.0.8-lp150.7.1
openSUSE:Leap 15.1libu2f-hostbefore 1.1.6-lp151.2.6.11.1.6-lp151.2.6.1
openSUSE:Leap 15.1pam_u2fbefore 1.0.8-lp151.2.3.11.0.8-lp151.2.3.1
openSUSE:Tumbleweedpam_u2fbefore 1.1.1-1.31.1.1-1.3
SUSE:Linux Enterprise Desktop 12 SP4libu2f-hostbefore 1.1.6-3.5.11.1.6-3.5.1
SUSE:Linux Enterprise Desktop 12 SP4pam_u2fbefore 1.0.8-3.3.11.0.8-3.3.1
SUSE:Linux Enterprise Module for Basesystem 15libu2f-hostbefore 1.1.6-3.6.11.1.6-3.6.1

Same product

yubico: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-12209Yubico pam-u2f 1.0.7 attempts parsing of the configured authfile (default $HOME/.config/Yubico/u2f_keys) as root (unless openasuser was enab
    31Monitor
  • CVE-2025-23013In Yubico pam-u2f before 1.3.1, local privilege escalation can sometimes occur.
    29Monitor
  • CVE-2021-31924Yubico pam-u2f before 1.1.1 has a logic issue that, depending on the pam-u2f configuration and the application used, could lead to a local P
    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 / packageFixed versionSource
debian:pam-u2f1.0.8-1 · Debian:12Package registry (OSV)
opensuse:libu2f-host1.1.6-lp151.2.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:pam_u2f1.0.8-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:libu2f-host1.1.6-3.5.1 · SUSE:Linux Enterprise Desktop 12 SP4Package registry (OSV)
suse:pam_u2f1.0.8-3.3.1 · SUSE:Linux Enterprise Desktop 12 SP4Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, 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

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

—

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records