From ${URL} : It was reported [1],[2] that xlockmore 5.43 fixes a NULL pointer dereference in situations where the crypt() call fails (the release notes indicate this is possible with glibc starting with version 2.17 due to crypt() failures returning EINVAL with a NULL return in certain situations). This could cause xlock to crash, which would allow for local users to obtain access to a locked desktop they would normally require a password to access. A patch [3] is available. This affects Fedora 19 as it provides glibc 2.17. Earlier versions are not affected. [1] http://www.tux.org/~bagleyd/xlock/xlockmore.README [2] http://www.openwall.com/lists/oss-security/2013/07/16/8 [3] http://sourceforge.net/projects/miscellaneouspa/files/glibc217/xlockmore-5.42-glibc217-crypt.diff @maintainer(s): after the bump, in case we need to stabilize the package, please say explicitly if it is ready for the stabilization or not.
Arch teams, please test and mark stable: =x11-misc/xlockmore-5.43 Stable KEYWORDS : alpha amd64 hppa ppc ppc64 sparc x86
Stable for HPPA.
amd64 stable
x86 stable
alpha stable
ppc64 stable
ppc stable
sparc stable
Thanks. GLSA vote: yes
GLSA vote: yes, request filed.
This issue was resolved and addressed in GLSA 201309-03 at http://security.gentoo.org/glsa/glsa-201309-03.xml by GLSA coordinator Sergey Popov (pinkbyte).