metadata/glsa/glsa-200905-04.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
68
69
70
71
72
73
74
75
76
77
78
79
80
81

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200905-04">
  <title>GnuTLS: Multiple vulnerabilities</title>
  <synopsis>
    Multiple vulnerabilities in GnuTLS might result in a Denial of Service,
    spoofing or the generation of invalid keys.
  </synopsis>
  <product type="ebuild">gnutls</product>
  <announced>2009-05-24</announced>
  <revised count="01">2009-05-24</revised>
  <bug>267774</bug>
  <access>remote</access>
  <affected>
    <package name="net-libs/gnutls" auto="yes" arch="*">
      <unaffected range="ge">2.6.6</unaffected>
      <vulnerable range="lt">2.6.6</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    GnuTLS is an Open Source implementation of the TLS 1.0 and SSL 3.0
    protocols.
    </p>
  </background>
  <description>
    <p>
    The following vulnerabilities were found in GnuTLS:
    </p>
    <ul>
    <li>Miroslav Kratochvil reported that lib/pk-libgcrypt.c does not
    properly handle corrupt DSA signatures, possibly leading to a
    double-free vulnerability (CVE-2009-1415).</li>
    <li>Simon Josefsson
    reported that GnuTLS generates RSA keys stored in DSA structures when
    creating a DSA key (CVE-2009-1416).</li>
    <li>Romain Francoise reported
    that the _gnutls_x509_verify_certificate() function in
    lib/x509/verify.c does not perform time checks, resulting in the
    "gnutls-cli" program accepting X.509 certificates with validity times
    in the past or future (CVE-2009-1417).</li>
    </ul>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could entice a user or automated system to process a
    specially crafted DSA certificate, possibly resulting in a Denial of
    Service condition. NOTE: This issue might have other unspecified impact
    including the execution of arbitrary code. Furthermore, a remote
    attacker could spoof signatures on certificates and the "gnutls-cli"
    application can be tricked into accepting an invalid certificate.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All GnuTLS users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-libs/gnutls-2.6.6"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1415">CVE-2009-1415</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1416">CVE-2009-1416</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1417">CVE-2009-1417</uri>
  </references>
  <metadata tag="requester" timestamp="2009-05-06T18:48:21Z">
    a3li
  </metadata>
  <metadata tag="submitter" timestamp="2009-05-07T11:40:21Z">
    a3li
  </metadata>
  <metadata tag="bugReady" timestamp="2009-05-24T11:17:39Z">
    p-y
  </metadata>
</glsa>