Fleet doesn’t validate a server’s certificate when connecting through SSH
- 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.10.12, 0.11.7, 0.12.2
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A vulnerability has been identified within Fleet where, by default, Fleet will automatically trust a remote server’s certificate when connecting through SSH if the certificate isn’t set in the `known_hosts` file. This could allow the execution of a man-in-the-middle (MitM) attack against Fleet. In case the server that is being connected to has a trusted entry in the known_hosts file, then Fleet will correctly check the authenticity of the presented certificate.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- github.com/rancher/fleet
From 0.9.0-rc.1 · fixed in 0.10.12; From 0.11.0 · fixed in 0.11.7; From 0.12.0 · fixed in 0.12.2
- github.com/rancher/fleetGo
From 0.9.0-rc.1 · fixed in 0.10.12
- github.com/rancher/fleetGo
From 0.11.0 · fixed in 0.11.7
- github.com/rancher/fleetGo
From 0.12.0 · fixed in 0.12.2
- github.com/rancher/fleetGo
From 0.9.0-rc.1 · fixed in 0.10.12; From 0.11.0 · fixed in 0.11.7; From 0.12.0 · fixed in 0.12.2