# CVE-2019-12210: Information disclosure in n/a

> Attackers can leak sensitive data or cause disk exhaustion via inherited file descriptors in Yubico pam-u2f when debug logging is enabled.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-12210, GHSA-pxf2-5pmm-5r8f

## What is CVE-2019-12210?

CVE-2019-12210 is a high-severity vulnerability in n/a, published on 4 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2019-12210?

It affects 1 product.


Products: Yubico Pam-U2f.

## How do I fix CVE-2019-12210?

Apply the vendor's patch.

## Is CVE-2019-12210 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12209](https://insights.sbomify.com/CVE-2019-12209/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12210 and fix it if it is affected.

What it is: CVE-2019-12210 is a high-severity vulnerability in n/a, published on 4 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12210 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-2019-12210/ (Markdown: https://insights.sbomify.com/CVE-2019-12210/index.md)
```

## Sources

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

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