LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9275: In check_user_token in util.c in the Yubico PAM module (aka pam_yubico) 2.18 through 2.25, successful login...

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9275 is a flaw in Yubico's PAM module where successful logins can leave a file handle open. Over time, this may expose a YubiKey device serial number from the auth mapping file or degrade login service availability by exhausting file descriptors.

Executive priority

Treat this as a targeted authentication infrastructure maintenance issue, not an emergency internet-wide exposure. Prioritize hosts that use YubiKey-backed PAM login and have high login volume or strict availability requirements.

Technical view

In pam_yubico 2.18 through 2.25, check_user_token in util.c can leak file descriptors to the auth mapping file after successful authentication. The documented impacts are information disclosure of a device serial number and denial of service from reaching the process file-descriptor limit.

Likely exposure

Exposure is limited to systems using the Yubico PAM module, pam_yubico, versions 2.18 through 2.25. The bundle does not identify broader products, CPEs, or downstream distribution package names.

Exploitation context

The source bundle does not show active exploitation, public exploit details, or CISA KEV listing. The condition described occurs after successful logins, so practical risk depends on PAM deployment, login volume, and file-descriptor limits.

Researcher notes

Evidence is clear on affected component, version range, vulnerable function, and impact class. The bundle lacks CVSS, CWE, detailed distribution advisory status, and exploit evidence, so validation should focus on deployed pam_yubico versions and whether the referenced fix is present.

Mitigation direction

  • Upgrade pam_yubico beyond the affected 2.18 through 2.25 range if vendor guidance confirms the fix.
  • Apply downstream Linux distribution security updates for pam_yubico where available.
  • Review Yubico issue and commit references for the specific file-descriptor leak fix.
  • Monitor authentication services for abnormal file-descriptor growth after logins.

Validation and detection

  • Inventory systems using pam_yubico and record installed package versions.
  • Check PAM configuration for active pam_yubico use on login paths.
  • Confirm whether vendor packages include Yubico commit 0f6ceabab0a8849b47f67d727aa526c2656089ba.
  • Review logs or process metrics for file-descriptor exhaustion symptoms in authentication services.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-9275 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.