CVE-2017-12197

N/A
Published: January 18, 2018 at 09:00 PM UTC
Updated: June 17, 2026 at 01:02 AM UTC
3 products affected across 3 vendorsDebian LinuxEnterprise LinuxLIBPAM4J

Using libpam4j by Red Hat, Inc.?

Get instant alerts when new vulnerabilities affect libpam4j - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%

Description

It was found that libpam4j up to and including 1.8 did not properly validate user accounts when authenticating. A user with a valid password for a disabled account would be able to bypass security restrictions and possibly access sensitive information.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (6)

Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2904
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2905
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2017:2906
x_refsource_CONFIRMIssue TrackingThird Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=1503103
Mailing Listx_refsource_MLISTThird Party Advisory
https://lists.debian.org/debian-lts-announce/2017/11/msg00008.html
Vendor Advisoryx_refsource_DEBIANThird Party Advisory
https://www.debian.org/security/2017/dsa-4025

CVSS

Confidentiality
PARTIAL
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-863CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card