A vulnerability has been reported in RSBAC, which can be exploited by malicious people to bypass certain security restrictions. The vulnerability is caused due to the incorrect use of the Linux Kernel Crypto API within certain User Management modules (e.g. rsbac_auth, pam_sbac.so, and pam_login). This can be exploited to bypass authentication by logging in with any password. The vulnerability is reported in versions 1.3.3 and 1.3.4 running a Linux 2.6.20 or later kernel. Solution: Update to version 1.3.5.
setting status. Hardened, please advise.
patch has been backported to 1.3.4 in rsbac-sources-2.6.21-r1 (~arch)
by the way, for the details: affected users are the ones using SHA1 hashes, UM module enabled, setuid allowed to that ID by the application used to login, and password set/reset/changed on 2.6.20 kernels prior to rsbac-sources-2.6.20-r1
(In reply to comment #3) > set/reset/changed on 2.6.20 kernels prior to rsbac-sources-2.6.20-r1 > 2.6.21-r1, sorry. too early in the morning.
closing this one without glsa since this is kernel stuff. feel free to reopen if you disagree.
