CVE-2005-2949: pam_per_user before 0.4 does not verify if the user name changes between authentication attempts and uses the

This month

HIGH 7.5DOWNGRADE

CVE-2005-2949 is a high-severity flaw (CVSS 7.5) affecting pam per user. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

pam_per_user before 0.4 does not verify if the user name changes between authentication attempts and uses the same subrequest handle, which allows remote attackers or local users to login as other users by using certain applications that allow the username to be changed during authentication, such as /bin/login.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.5 (High)
EPSS exploit chance	1.6% (top 24%)
CISA exploited list	No
Published	2005-09-16
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: mark d. roth

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-09-16 22:03 UTCPublished CVE record published
2026-06-16 22:15 UTCUpdated Record last modified

mark d. roth pam per user DOWNGRADE

Affected: 0.1 · 0.2 · 0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1

1. Check installed version

apt-cache policy pam-per-user || rpm -q pam-per-user || pam-per-user --version

2. No fixed release: DOWNGRADE to a release before 0.1 (Debian / Ubuntu)

apt-cache madison pam-per-user sudo apt install pam-per-user=<VERSION_BEFORE_0.1> sudo apt-mark hold pam-per-user

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pam-per-user sudo dnf downgrade pam-per-user-<VERSION_BEFORE_0.1> sudo dnf versionlock add pam-per-user

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-2949?

pam per user: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-2949 being exploited?

CVE-2005-2949 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-2949 affect?

CVE-2005-2949 affects pam per user. Severity is high (CVSS 7.5). pam_per_user before 0.4 does not verify if the user name changes between authentication attempts and uses the same subrequest handle, which allows remote attackers or local users to login as other users by using certain applications that al

How urgent is CVE-2005-2949?

Priority 45/100. High severity

References

← Back to latest CVEs