# CVE-2025-23013: Auth bypass in pam-u2f

> Local attackers can bypass authentication and escalate privileges in specific configurations of the Yubico PAM module.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jan 2025
- **Updated:** 3 Feb 2025
- **Also known as:** DEBIAN-CVE-2025-23013, DLA-4040-1, DSA-5853-1, GHSA-wwr4-cj7g-985f, SUSE-SU-2025:0167-1, SUSE-SU-2025:0192-1, SUSE-SU-2025:0198-1, SUSE-SU-2025:0200-1, SUSE-SU-2025:20132-1, SUSE-SU-2025:20231-1, UBUNTU-CVE-2025-23013, USN-7806-1, openSUSE-SU-2025:14650-1

## What is CVE-2025-23013?

CVE-2025-23013 is a high-severity authentication bypass vulnerability in Yubico pam-u2f, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Yubico pam-u2f before 1.3.1, local privilege escalation can sometimes occur. This product implements a Pluggable Authentication Module (PAM) that can be deployed to support authentication using a YubiKey or other FIDO compliant authenticators on macOS or Linux. This software package has an issue that allows for an authentication bypass in some configurations. An attacker would require the ability to access the system as an unprivileged user. Depending on the configuration, the attacker may also need to know the user's password.

Weakness: CWE-394 (Unexpected Status Code or Return Value)

## Which versions are affected by CVE-2025-23013?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam_u2f` | SUSE:Enterprise Storage 7.1 | All versions | 1.0.8-150000.3.6.1 |
| `pam_u2f` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 1.0.8-150000.3.6.1 |
| `pam_u2f` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.2.0-150600.10.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 1.0.8-3.6.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 1.0.8-150000.3.6.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server 15 SP5-LTSS | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 1.0.8-3.6.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 1.0.8-150000.3.6.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Enterprise Server for SAP Applications 15 SP5 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Linux Micro 6.0 | All versions | 1.3.2-1.1 |
| `pam_u2f` | SUSE:Linux Micro 6.1 | All versions | 1.3.0-slfo.1.1_2.1 |
| `pam_u2f` | SUSE:Manager Proxy 4.3 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | SUSE:Manager Server 4.3 | All versions | 1.2.0-150400.4.5.1 |
| `pam_u2f` | openSUSE:Leap 15.6 | All versions | 1.2.0-150600.10.5.1 |
| `pam_u2f` | openSUSE:Tumbleweed | All versions | 1.3.1-1.1 |

## How do I fix CVE-2025-23013?

Upgrade to a fixed version.

## Is CVE-2025-23013 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-23013 and fix it if it is affected.

What it is: CVE-2025-23013 is a high-severity authentication bypass vulnerability in Yubico pam-u2f, published on 15 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-23013 in the wild and no public exploit code.

Affected product: Yubico pam-u2f. 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-2025-23013/ (Markdown: https://insights.sbomify.com/CVE-2025-23013/index.md)
```

## Sources

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

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