Steve doesn’t verify a server’s certificate and is susceptible to man-in-the-middle (MitM) attacks
SUSE steve
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/steve Go |
|
|
SUSE steve
| Product | Affected | Fixed in |
|---|---|---|
| github.com/rancher/steve Go |
|
|
0.5.13A 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.
From the CVE record · suse
Steve used an insecure default that did not validate the remote server’s certificate during TLS connections. An attacker positioned between Steve and the remote server could perform a man-in-the-middle attack against services using Steve; the input does not specify authentication or user-interaction requirements.
Teams running SUSE steve or Go package github.com/rancher/steve should check versions >=0.2.0 <0.2.1, >=0.3.0 <0.3.3, >=0.4.0 <0.4.4, and >=0.5.0 <0.5.13.