CVE-2023-32198GHSA-95FC-G4GJ-MQMXGO-2025-3648
Steve doesn’t verify a server’s certificate and is susceptible to man-in-the-middle (MitM) attacks
- 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 0.2.1, 0.3.3, 0.4.4, 0.5.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A vulnerability has been identified in Steve where by default it was using an insecure option that did not validate the certificate presented by the remote server while performing a TLS connection. This could allow the execution of a man-in-the-middle (MitM) attack against services using Steve.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- github.com/rancher/steve
From 0.2.0 · fixed in 0.2.1; From 0.3.0 · fixed in 0.3.3; From 0.4.0 · fixed in 0.4.4; From 0.5.0 · fixed in 0.5.13
- github.com/rancher/steveGo
From 0.2.0 · fixed in 0.2.1
- github.com/rancher/steveGo
From 0.3.0 · fixed in 0.3.3
- github.com/rancher/steveGo
From 0.4.0 · fixed in 0.4.4
- github.com/rancher/steveGo
From 0.5.0 · fixed in 0.5.13
- github.com/rancher/steveGo
All versions
- github.com/rancher/steveGo
From 0.2.0 · fixed in 0.2.1; From 0.4.0 · fixed in 0.4.4; From 0.5.0 · fixed in 0.5.13