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.
References
Link | Resource |
---|---|
https://hackerone.com/reports/1898475 | Exploit 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 |
https://security.netapp.com/advisory/ntap-20230420-0010/ | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
AND |
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
AND |
|
Configuration 8 (hide)
AND |
|
Configuration 9 (hide)
|
History
No history.
Information
Published : 2023-03-30 20:15
Updated : 2024-03-27 14:46
NVD link : CVE-2023-27538
Mitre link : CVE-2023-27538
CVE.ORG link : CVE-2023-27538
JSON object : View
Products Affected
splunk
- universal_forwarder
netapp
- h300s_firmware
- h410s_firmware
- clustered_data_ontap
- active_iq_unified_manager
- h500s_firmware
- h300s
- h500s
- h700s_firmware
- h700s
- h410s
broadcom
- brocade_fabric_operating_system_firmware
fedoraproject
- fedora
haxx
- libcurl
debian
- debian_linux