From ${URL} : It was found that in pam_userdb module for Pam, password hashes weren't compared case-sensitively, which could lead to acceptance of hashes for completely different passwords, which shouldn't be accepted. After hashing the user's password with crypt(), pam_userdb compares the result to the stored hash case-insensitively with strncasecmp(), which should be avoided, as it could result in an increased possibility of a successful brute-force attack. References: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731368 @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
Created attachment 381764 [details, diff] pam-1.1.8-cve-2013-7041.patch
CVE-2013-7041 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-7041): The pam_userdb module for Pam uses a case-insensitive method to compare hashed passwords, which makes it easier for attackers to guess the password via a brute force attack.
Upstream patch, https://git.fedorahosted.org/cgit/linux-pam.git/commit/?id=57a1e2b. Red-Hat considering it a very low issues. Maintainers please advise what is your opinion on this?
should be all set now in the tree; thanks for the report! Commit message: Fix from upstream for password case checks http://sources.gentoo.org/sys-libs/pam/files/pam-1.1.8-CVE-2013-7041.patch?rev=1.1 http://sources.gentoo.org/sys-libs/pam/pam-1.1.8-r3.ebuild?rev=1.1
sys-libs/pam-1.1.8-r3 has been in tree for quite some time. @arches, please stabilize.
pam-1.2.1 is already stable
Added to existing GLSA.
Cleanup complete: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a0819b4caa858b34434c1d21217ffea94d76215b
This issue was resolved and addressed in GLSA 201605-05 at https://security.gentoo.org/glsa/201605-05 by GLSA coordinator Yury German (BlueKnight).
