transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.0.8, 2.1.5, 2.2.3, 2.3.2, 2.4.1, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 on Exploit-DB, 2 proofs of concept on GitHub
Summary
transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.
Timeline
- CVE published
- Public exploit on Exploit-DB
EDB-45712
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- n/a n/a
Version range not reported
- paramikoPyPI
From 2.0.0 · fixed in 2.0.8
- paramikoPyPI
From 2.1.0 · fixed in 2.1.5
- paramikoPyPI
From 2.2.0 · fixed in 2.2.3
- paramikoPyPI
From 2.3.0 · fixed in 2.3.2
- paramikoPyPI
From 2.4.0 · fixed in 2.4.1
- paramikoPyPI
From 1.18.0 · fixed in 1.18.5
- paramikoPyPI
fixed in 1.17.6
- paramikoPyPI
fixed in 1.17.6; From 1.18.0 · fixed in 1.18.5; From 2.0.0 · fixed in 2.0.8; From 2.1.0 · fixed in 2.1.5; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.2