SSH improper host validation
curl
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
curl
| Product | Affected | Fixed in |
|---|---|---|
| curl curl |
| No fix yet |
| curl curl |
| No fix yet |
| curl curl |
|
8.19.08.18.08.17.08.16.08.15.0| No fix yet |
When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.
From the CVE record · curl
A libcurl-based application using the CURLOPT_SSH_KEYFUNCTION callback for SCP or SFTP transfers may silently accept an untrusted server if its host key type differs from the type recorded for that host in known_hosts. The connection can succeed without warning, creating a potential man-in-the-middle risk.
Engineers running curl or libcurl-based applications that use CURLOPT_SSH_KEYFUNCTION for SCP or SFTP transfers should check their deployments; affected versions were not provided.