Authentication Bypass in libpam4j <= 1.8
libpam4j versions up to and including 1.8 fail to properly validate the status of user accounts during authentication. Specifically, the library allows authentication to succeed for users with valid passwords even if their accounts are disabled, due to insufficient checks on account status during the authentication process.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An attacker with knowledge of a valid password for a disabled account can successfully authenticate and gain access to resources that should be protected, potentially leading to unauthorized access to sensitive information and privilege escalation.
If you can’t patch tonight, do this now.
As an interim measure, restrict access to systems using libpam4j for authentication, and monitor for attempts to authenticate with disabled accounts. Consider disabling or removing accounts at the system level, not just marking them as disabled in the application.
Patch, then assume compromise.
Upgrade libpam4j to a version after 1.8 where proper account status validation is implemented during authentication. Ensure that the authentication logic checks both password validity and account status (e.g., disabled, locked) before granting access.
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.