glsa-200907-09.xml


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
65
66
67

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">

<glsa id="200907-09">
  <title>Cyrus-SASL: Execution of arbitrary code</title>
  <synopsis>
    A buffer overflow in Cyrus-SASL might allow for the execution of arbitrary
    code in applications or daemons that authenticate using SASL.
  </synopsis>
  <product type="ebuild">cyrus-sasl</product>
  <announced>July 12, 2009</announced>
  <revised>July 12, 2009: 01</revised>
  <bug>270261</bug>
  <access>remote</access>
  <affected>
    <package name="dev-libs/cyrus-sasl" auto="yes" arch="*">
      <unaffected range="ge">2.1.23</unaffected>
      <vulnerable range="lt">2.1.23</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    Cyrus-SASL is an implementation of the Simple Authentication and
    Security Layer.
    </p>
  </background>
  <description>
    <p>
    James Ralston reported that in certain situations, Cyrus-SASL does not
    properly terminate strings which can result in buffer overflows when
    performing Base64 encoding.
    </p>
  </description>
  <impact type="high">
    <p>
    A remote unauthenticated user might send specially crafted packets to a
    daemon using Cyrus-SASL, possibly resulting in the execution of
    arbitrary code with the privileges of the user running the daemon or a
    Denial of Service.
    </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 &quot;&gt;=dev-libs/cyrus-sasl-2.1.23&quot;</code>
  </resolution>
  <references>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0688">CVE-2009-0688</uri>
  </references>
  <metadata tag="requester" timestamp="Thu, 09 Jul 2009 18:32:29 +0000">
    rbu
  </metadata>
  <metadata tag="submitter" timestamp="Thu, 09 Jul 2009 21:10:28 +0000">
    rbu
  </metadata>
  <metadata tag="bugReady" timestamp="Fri, 10 Jul 2009 10:41:22 +0000">
    rbu
  </metadata>
</glsa>