blob: bcb1ffd911b2d1537950034b8a9b67069da2705a (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200803-07">
<title>Paramiko: Information disclosure</title>
<synopsis>
Unsafe randomness usage in Paramiko may allow access to sensitive
information.
</synopsis>
<product type="ebuild">paramiko</product>
<announced>March 03, 2008</announced>
<revised>March 03, 2008: 01</revised>
<bug>205777</bug>
<access>remote</access>
<affected>
<package name="dev-python/paramiko" auto="yes" arch="*">
<unaffected range="ge">1.7.2</unaffected>
<vulnerable range="lt">1.7.2</vulnerable>
</package>
</affected>
<background>
<p>
Paramiko is a Secure Shell Server implementation written in Python.
</p>
</background>
<description>
<p>
Dwayne C. Litzenberger reported that the file "common.py" does not
properly use RandomPool when using threads or forked processes.
</p>
</description>
<impact type="low">
<p>
A remote attacker could predict the values generated by applications
using Paramiko for encryption purposes, potentially gaining access to
sensitive information.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All Paramiko users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-python/paramiko-1.7.2"</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0299">CVE-2008-0299</uri>
</references>
<metadata tag="requester" timestamp="Mon, 11 Feb 2008 18:32:09 +0000">
jaervosz
</metadata>
<metadata tag="bugReady" timestamp="Mon, 11 Feb 2008 18:33:24 +0000">
jaervosz
</metadata>
<metadata tag="submitter" timestamp="Thu, 28 Feb 2008 12:43:49 +0000">
p-y
</metadata>
</glsa>
|
GitWeb
