GHSA-232r-66cg-79px
CRITICALGHSA-232r-66cg-79px is a critical-severity (CVSS 9.8) Improper Authentication vulnerability in paramiko. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-232r-66cg-79px is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Paramiko not properly checking authentication before processing other requests
Blast Radius
paramiko🐍paramiko🐍paramiko🐍paramiko🐍paramiko🐍paramiko🐍paramikoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | paramiko | ≥ 2.0.0&&< 2.0.8 | 2.0.8 |
| 🐍PyPI | paramiko | ≥ 2.1.0&&< 2.1.5 | 2.1.5 |
| 🐍PyPI | paramiko | ≥ 2.2.0&&< 2.2.3 | 2.2.3 |
| 🐍PyPI | paramiko | ≥ 2.3.0&&< 2.3.2 | 2.3.2 |
| 🐍PyPI | paramiko | ≥ 2.4.0&&< 2.4.1 | 2.4.1 |
| 🐍PyPI | paramiko | ≥ 1.18.0&&< 1.18.5 | 1.18.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Paramiko 2.4.1 - Authentication Bypass
by Adam Brown · Oct 29, 2018
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for paramiko. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update paramiko to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-232r-66cg-79px is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-232r-66cg-79px is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-232r-66cg-79px. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-232r-66cg-79px in your dependencies?
O3 detects GHSA-232r-66cg-79px across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.