summaryrefslogtreecommitdiff
blob: 4cedffb8c1de505f3d58df3c21fe1beda72563ec (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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200610-11">
  <title>OpenSSL: Multiple vulnerabilities</title>
  <synopsis>
    OpenSSL contains multiple vulnerabilities including the possible remote
    execution of arbitrary code.
  </synopsis>
  <product type="ebuild">openssl</product>
  <announced>2006-10-24</announced>
  <revised count="01">2006-10-24</revised>
  <bug>145510</bug>
  <access>remote</access>
  <affected>
    <package name="dev-libs/openssl" auto="yes" arch="*">
      <unaffected range="ge">0.9.8d</unaffected>
      <unaffected range="rge">0.9.7l</unaffected>
      <vulnerable range="lt">0.9.8d</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    OpenSSL is a toolkit implementing the Secure Sockets Layer, Transport
    Layer Security protocols and a general-purpose cryptography library.
    </p>
  </background>
  <description>
    <p>
    Tavis Ormandy and Will Drewry, both of the Google Security Team,
    discovered that the SSL_get_shared_ciphers() function contains a buffer
    overflow vulnerability, and that the SSLv2 client code contains a flaw
    leading to a crash. Additionally Dr. Stephen N. Henson found that the
    ASN.1 handler contains two Denial of Service vulnerabilities: while
    parsing an invalid ASN.1 structure and while handling certain types of
    public key.
    </p>
  </description>
  <impact type="high">
    <p>
    An attacker could trigger the buffer overflow vulnerability by sending
    a malicious suite of ciphers to an application using the vulnerable
    function, and thus execute arbitrary code with the rights of the user
    running the application. An attacker could also consume CPU and/or
    memory by exploiting the Denial of Service vulnerabilities. Finally a
    malicious server could crash a SSLv2 client through the SSLv2
    vulnerability.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All OpenSSL 0.9.8 users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=dev-libs/openssl-0.9.8d"</code>
    <p>
    All OpenSSL 0.9.7 users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=dev-libs/openssl-0.9.7l"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2937">CVE-2006-2937</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2940">CVE-2006-2940</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3738">CVE-2006-3738</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4343">CVE-2006-4343</uri>
  </references>
  <metadata tag="requester" timestamp="2006-09-28T15:36:31Z">
    vorlon078
  </metadata>
  <metadata tag="submitter" timestamp="2006-10-13T16:05:39Z">
    falco
  </metadata>
  <metadata tag="bugReady" timestamp="2006-10-24T10:05:56Z">
    falco
  </metadata>
</glsa>