Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1503103 - (CVE-2017-12197) CVE-2017-12197 libpam4j: Account check bypass
CVE-2017-12197 libpam4j: Account check bypass
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20171017,repor...
: Security
: 1502898 (view as bug list)
Depends On: 1511366 1639395
Blocks: 1491381
  Show dependency treegraph
 
Reported: 2017-10-17 07:42 EDT by Adam Mariš
Modified: 2018-10-15 11:38 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
It was found that libpam4j 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.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-13 21:59:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2904 normal SHIPPED_LIVE Moderate: rh-sso7-keycloak security update 2017-10-17 19:53:00 EDT
Red Hat Product Errata RHSA-2017:2905 normal SHIPPED_LIVE Moderate: rh-sso7-keycloak security update 2017-10-17 19:53:19 EDT
Red Hat Product Errata RHSA-2017:2906 normal SHIPPED_LIVE Moderate: Red Hat Single Sign-On security update 2017-10-17 19:42:35 EDT

  None (edit)
Description Adam Mariš 2017-10-17 07:42:06 EDT
PAM.authentication() does not call pam_acct_mgmt(). As a consequence, the PAM account is not properly verified. Any user with a valid password but with deactivated or disabled account is able to log in.
Comment 1 Adam Mariš 2017-10-17 07:42:13 EDT
Acknowledgments:

Name: Christian Heimes (Red Hat)
Comment 2 Chess Hazlett 2017-10-17 09:00:50 EDT
*** Bug 1502898 has been marked as a duplicate of this bug. ***
Comment 3 errata-xmlrpc 2017-10-17 15:43:10 EDT
This issue has been addressed in the following products:

  Red Hat Single Sign-On

Via RHSA-2017:2906 https://access.redhat.com/errata/RHSA-2017:2906
Comment 4 errata-xmlrpc 2017-10-17 15:54:11 EDT
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.1 for RHEL 6

Via RHSA-2017:2904 https://access.redhat.com/errata/RHSA-2017:2904
Comment 5 errata-xmlrpc 2017-10-17 15:54:42 EDT
This issue has been addressed in the following products:

  Red Hat Single Sign-On 7.1 for RHEL 7

Via RHSA-2017:2905 https://access.redhat.com/errata/RHSA-2017:2905
Comment 6 Markus Koschany 2017-11-03 16:00:47 EDT
Would it be possible to share the patch for this security issue or has someone forwarded it upstream already?
Comment 8 Chess Hazlett 2017-11-07 13:25:38 EST
It's been resolved in upstream, keycloak 3.3.0.Final. [https://issues.jboss.org/browse/KEYCLOAK-5551]
Comment 9 Tomas Hoger 2017-11-09 04:00:45 EST
Created libpam4j tracking bugs for this issue:

Affects: fedora-all [bug 1511366]
Comment 10 Chess Hazlett 2017-11-13 21:59:27 EST
closing, this has been resolved in RHSSO and Fedora trackers filed.
Comment 11 Andrej Nemec 2018-10-15 11:38:01 EDT
Created jenkins-pam-auth-plugin tracking bugs for this issue:

Affects: fedora-all [bug 1639395]

Note You need to log in before you can comment on or make changes to this bug.