# CVE-2018-9275: Information disclosure in n/a

> Attackers can leak file descriptors to disclose device serial numbers or cause denial of service via resource exhaustion in the Yubico PAM module.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-9275, GHSA-24jw-8jpm-q7p5, UBUNTU-CVE-2018-9275, openSUSE-SU-2024:11146-1

## What is CVE-2018-9275?

CVE-2018-9275 is a high-severity vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In check_user_token in util.c in the Yubico PAM module (aka pam_yubico) 2.18 through 2.25, successful logins can leak file descriptors to the auth mapping file, which can lead to information disclosure (serial number of a device) and/or DoS (reaching the maximum number of file descriptors).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-9275?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam_yubico` | openSUSE:Tumbleweed | All versions | 2.27-1.5 |

Products: Yubico Yubico Pam.

## How do I fix CVE-2018-9275?

Upgrade to a fixed version.

## Is CVE-2018-9275 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9275 and fix it if it is affected.

What it is: CVE-2018-9275 is a high-severity vulnerability in n/a, published on 4 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-9275 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-2018-9275/ (Markdown: https://insights.sbomify.com/CVE-2018-9275/index.md)
```

## Sources

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

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