summaryrefslogtreecommitdiff
blob: 9e2d24bdfd9a524b7ed6d0eca7b9edfd02c5c253 (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
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200908-01">
  <title>OpenSC: Multiple vulnerabilities</title>
  <synopsis>
    Multiple vulnerabilities were found in OpenSC.
  </synopsis>
  <product type="ebuild">opensc</product>
  <announced>2009-08-01</announced>
  <revised count="01">2009-08-01</revised>
  <bug>260514</bug>
  <bug>269920</bug>
  <access>local</access>
  <affected>
    <package name="dev-libs/opensc" auto="yes" arch="*">
      <unaffected range="ge">0.11.8</unaffected>
      <vulnerable range="lt">0.11.8</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    OpenSC provides a set of libraries and utilities to access smart cards.
    </p>
  </background>
  <description>
    <p>
    Multiple vulnerabilities were found in OpenSC:
    </p>
    <ul>
    <li>b.badrignans discovered that OpenSC incorrectly initialises private
    data objects (CVE-2009-0368).</li>
    <li>Miquel Comas Marti discovered
    that src/tools/pkcs11-tool.c in pkcs11-tool in OpenSC 0.11.7, when used
    with unspecified third-party PKCS#11 modules, generates RSA keys with
    incorrect public exponents (CVE-2009-1603).</li>
    </ul>
  </description>
  <impact type="normal">
    <p>
    The first vulnerabilty allows physically proximate attackers to bypass
    intended PIN requirements and read private data objects. The second
    vulnerability allows attackers to read the cleartext form of messages
    that were intended to be encrypted.
    </p>
    <p>
    NOTE: Smart cards which were initialised using an affected version of
    OpenSC need to be modified or re-initialised. See the vendor's advisory
    for details.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All OpenSC users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=dev-libs/opensc-0.11.8"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0368">CVE-2009-0368</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-1603">CVE-2009-1603</uri>
    <uri link="http://www.opensc-project.org/pipermail/opensc-announce/2009-February/000023.html">OpenSC Security Advisory</uri>
  </references>
  <metadata tag="requester" timestamp="2009-06-24T16:49:20Z">
    keytoaster
  </metadata>
  <metadata tag="submitter" timestamp="2009-07-29T17:15:19Z">
    keytoaster
  </metadata>
  <metadata tag="bugReady" timestamp="2009-08-01T12:35:17Z">
    keytoaster
  </metadata>
</glsa>