An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.
The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
| Link | Tags |
|---|---|
| https://hackerone.com/reports/1898475 | exploit third party advisory |
| https://security.netapp.com/advisory/ntap-20230420-0010/ | third party advisory |
| https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html | mailing list |
| https://security.gentoo.org/glsa/202310-12 | third party advisory vendor advisory |