blob: 7410ac1f40222798711e50d53da8f45667274249 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200612-19">
<title>pam_ldap: Authentication bypass vulnerability</title>
<synopsis>
pam_ldap contains a vulnerability that may allow a remote user with a
locked account to gain unauthorized system access.
</synopsis>
<product type="ebuild">pam_ldap</product>
<announced>December 20, 2006</announced>
<revised>December 20, 2006: 01</revised>
<bug>153916</bug>
<access>remote</access>
<affected>
<package name="sys-auth/pam_ldap" auto="yes" arch="*">
<unaffected range="ge">183</unaffected>
<vulnerable range="lt">183</vulnerable>
</package>
</affected>
<background>
<p>
pam_ldap is a Pluggable Authentication Module which allows
authentication against LDAP directories.
</p>
</background>
<description>
<p>
Steve Rigler discovered that pam_ldap does not correctly handle
"PasswordPolicyResponse" control responses from an LDAP directory. This
causes the pam_authenticate() function to always succeed, even if the
previous authentication failed.
</p>
</description>
<impact type="low">
<p>
A locked user may exploit this vulnerability to bypass the LDAP
authentication mechanism, possibly gaining unauthorized access to the
system.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All pam_ldap users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-auth/pam_ldap-183"</code>
</resolution>
<references>
<uri link="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5170">CVE-2006-5170</uri>
</references>
<metadata tag="submitter" timestamp="Tue, 19 Dec 2006 16:57:27 +0000">
falco
</metadata>
<metadata tag="bugReady" timestamp="Tue, 19 Dec 2006 16:58:04 +0000">
falco
</metadata>
</glsa>
|