Skip to main content
Mallory
MediumVulnerability

CVE-2017-12197: Authentication Bypass in libpam4j <= 1.8

Published Jan 18, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Debian ProjectLibpam4j ProjectRed Hat
IdentifiersCVE-2017-12197CWE-287

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
Libpam4j ProjectLibpam4japplication
Red HatRed Hat Enterprise Linuxoperating_system
FAQ

Frequently asked questions

Is CVE-2017-12197 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-12197 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-12197?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2017-12197.
Is there a patch for CVE-2017-12197?
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.
What products are affected by CVE-2017-12197?
Libpam4j Project Libpam4j, Debian Project Debian Linux, and Red Hat Enterprise Linux.
How severe is CVE-2017-12197?
CVE-2017-12197 has a CVSS v3 score of 6.5 (Medium) and an EPSS score of 1.5% (75th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.