HighGHSA-wqmm-q65g-2hqrCVE-2008-0299PYSEC-2008-8

Paramiko Unsafe randomness usage may allow access to sensitive information

Published 1 May 2022 · Updated 8 Oct 2024

Is your project on an affected paramiko?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.7.1-3
Fixed in
1.7.1-3
Update to the fixed version for your release line, for example:pip install 'paramiko>=1.7.1-3'

Details

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.

Is GHSA-wqmm-q65g-2hqr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected paramiko, and gives you the command that fixes it.

More advisories for paramiko

  • LowCVE-2026-44405Paramiko rsakey.py allows the SHA-1 algorithm · 6 May 2026
  • MediumCVE-2023-48795Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin · 18 Dec 2023
  • HighCVE-2022-24302Race Condition in Paramiko · 19 Mar 2022
  • HighCVE-2018-1000805Paramiko Authentication Bypass vulnerability · 10 Oct 2018
  • CriticalCVE-2018-7750Paramiko not properly checking authentication before processing other requests · 12 Jul 2018
paramiko security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.