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
84
85
86
87
88
89
90
91
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201402-24">
<title>GnuPG, Libgcrypt: Multiple vulnerabilities</title>
<synopsis>Multiple vulnerabilities have been discovered in GnuPG and
Libgcrypt, which may result in execution of arbitrary code, Denial of
Service, or the disclosure of private keys.
</synopsis>
<product type="ebuild">gnupg libgcrypt</product>
<announced>2014-02-21</announced>
<revised count="3">2016-08-24</revised>
<bug>449546</bug>
<bug>478184</bug>
<bug>484836</bug>
<bug>487230</bug>
<bug>494658</bug>
<access>local, remote</access>
<affected>
<package name="app-crypt/gnupg" auto="yes" arch="*">
<unaffected range="ge">2.0.22</unaffected>
<unaffected range="rge">1.4.16</unaffected>
<unaffected range="rge">1.4.17</unaffected>
<unaffected range="rge">1.4.18</unaffected>
<unaffected range="rge">1.4.19</unaffected>
<unaffected range="rge">1.4.20</unaffected>
<unaffected range="rge">1.4.21</unaffected>
<vulnerable range="lt">2.0.22</vulnerable>
</package>
<package name="dev-libs/libgcrypt" auto="yes" arch="*">
<unaffected range="ge">1.5.3</unaffected>
<vulnerable range="lt">1.5.3</vulnerable>
</package>
</affected>
<background>
<p>The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of
cryptographic software. Libgcrypt is a cryptographic library based on
GnuPG.
</p>
</background>
<description>
<p>Multiple vulnerabilities have been discovered in GnuPG and Libgcrypt.
Please review the CVE identifiers referenced below for details.
</p>
</description>
<impact type="normal">
<p>An unauthenticated remote attacker may be able to execute arbitrary code
with the privileges of the user running GnuPG, cause a Denial of Service
condition, or bypass security restrictions. Additionally, a side-channel
attack may allow a local attacker to recover a private key, please review
“Flush+Reload: a High Resolution, Low Noise, L3 Cache Side-Channel
Attack” in the References section for further details.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All GnuPG 2.0 users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.0.22"
</code>
<p>All GnuPG 1.4 users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.16"
</code>
<p>All Libgcrypt users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-libs/libgcrypt-1.5.3"
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-6085">CVE-2012-6085</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4242">CVE-2013-4242</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4351">CVE-2013-4351</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4402">CVE-2013-4402</uri>
<uri link="https://eprint.iacr.org/2013/448">Flush+Reload: a High
Resolution, Low Noise, L3 Cache Side-Channel Attack
</uri>
</references>
<metadata tag="requester" timestamp="2013-01-15T21:37:26Z">ackle</metadata>
<metadata tag="submitter" timestamp="2016-08-24T12:08:25Z">ackle</metadata>
</glsa>
|
GitWeb