CVE-2008-0299: Paramiko Unsafe randomness usage may allow access to sensitive information

CVE-2008-0299 · Severity: low · CVSS 3.1 · Published 2008-01-16

common.py in Paramiko 1.7.1 and earlier, when using threads or forked processes, does not properly use RandomPool, which allows one session to obtain sensitive information from another session by predicting the state of the pool.

Technologies: paramiko (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2008-0299 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2008-0299 being exploited in the wild.
How severe is CVE-2008-0299?
Low severity, with a CVSS score of 3.1, published 16 January 2008.
Which products and versions are affected?
paramiko (PyPI) ECOSYSTEM:introduced=0,fixed=1.7.1-3, ECOSYSTEM:introduced=0,fixed=1.7.2.
Is there a fix for CVE-2008-0299?
Yes. paramiko (PyPI): upgrade to 1.7.1-3, 1.7.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2008-0299?
Check whether you run paramiko (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • paramiko (PyPI): upgrade to 1.7.1-3, 1.7.2 or later
    pip install "paramiko>=1.7.2"

Affected products

  • paramiko (PyPI) ECOSYSTEM:introduced=0,fixed=1.7.1-3, ECOSYSTEM:introduced=0,fixed=1.7.2

Identifiers

  • CVE-2008-0299
  • GHSA-wqmm-q65g-2hqr
  • PYSEC-2008-8

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.