blob: 658ec5e207ff468338fb59750fb21c10ff7b9417 (
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
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201309-01">
<title>Cyrus-SASL: Denial of service</title>
<synopsis>A NULL pointer dereference in Cyrus-SASL may allow remote attackers
to cause a Denial of Service condition.
</synopsis>
<product type="ebuild">cyrus-sasl</product>
<announced>2013-09-01</announced>
<revised count="1">2013-09-01</revised>
<bug>476764</bug>
<access>remote</access>
<affected>
<package name="dev-libs/cyrus-sasl" auto="yes" arch="*">
<unaffected range="ge">2.1.26-r3</unaffected>
<vulnerable range="lt">2.1.26-r3</vulnerable>
</package>
</affected>
<background>
<p>Cyrus-SASL is an implementation of the Simple Authentication and
Security Layer.
</p>
</background>
<description>
<p>In the GNU C Library (glibc) from version 2.17 onwards, the crypt()
function call can return NULL when the salt violates specifications or
the system is in FIPS-140 mode and a DES or MD5 hashed password is
passed. When Cyrus-SASL’s authentication mechanisms call crypt(), a
NULL may be returned.
</p>
</description>
<impact type="normal">
<p>A remote attacker could trigger this vulnerability to cause a Denial of
Service condition.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All Cyrus-SASL users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-libs/cyrus-sasl-2.1.26-r3"
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4122">CVE-2013-4122</uri>
</references>
<metadata tag="requester" timestamp="2013-08-23T14:52:45Z">
creffett
</metadata>
<metadata tag="submitter" timestamp="2013-09-01T19:36:23Z">
creffett
</metadata>
</glsa>
|
GitWeb
