CVE-2023-38545

This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.
References
Link Resource
http://seclists.org/fulldisclosure/2024/Jan/34 Mailing List Third Party Advisory
http://seclists.org/fulldisclosure/2024/Jan/37 Mailing List Third Party Advisory
http://seclists.org/fulldisclosure/2024/Jan/38 Mailing List Third Party Advisory
https://curl.se/docs/CVE-2023-38545.html Patch Third Party Advisory
https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/ Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20231027-0009/ Third Party Advisory
https://security.netapp.com/advisory/ntap-20240201-0005/ Third Party Advisory
https://support.apple.com/kb/HT214036 Third Party Advisory
https://support.apple.com/kb/HT214057 Third Party Advisory
https://support.apple.com/kb/HT214058 Third Party Advisory
https://support.apple.com/kb/HT214063 Third Party Advisory
https://www.secpod.com/blog/high-severity-heap-buffer-overflow-vulnerability/ Patch Third Party Advisory
http://seclists.org/fulldisclosure/2024/Jan/34 Mailing List Third Party Advisory
http://seclists.org/fulldisclosure/2024/Jan/37 Mailing List Third Party Advisory
http://seclists.org/fulldisclosure/2024/Jan/38 Mailing List Third Party Advisory
https://curl.se/docs/CVE-2023-38545.html Patch Third Party Advisory
https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/ Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20231027-0009/ Third Party Advisory
https://security.netapp.com/advisory/ntap-20240201-0005/ Third Party Advisory
https://support.apple.com/kb/HT214036 Third Party Advisory
https://support.apple.com/kb/HT214057 Third Party Advisory
https://support.apple.com/kb/HT214058 Third Party Advisory
https://support.apple.com/kb/HT214063 Third Party Advisory
https://www.secpod.com/blog/high-severity-heap-buffer-overflow-vulnerability/ Patch Third Party Advisory
https://github.com/UTsweetyfish/CVE-2023-38545
https://github.com/bcdannyboy/CVE-2023-38545
https://github.com/dbrugman/CVE-2023-38545-POC
Configurations

Configuration 1 (hide)

cpe:2.3:a:haxx:libcurl:*:*:*:*:*:*:*:*

Configuration 2 (hide)

cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*

Configuration 3 (hide)

OR cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:vmware_vsphere:*:*
cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:windows:*:*
cpe:2.3:a:netapp:oncommand_insight:-:*:*:*:*:*:*:*
cpe:2.3:a:netapp:oncommand_workflow_automation:-:*:*:*:*:*:*:*

Configuration 4 (hide)

OR cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10_21h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_10_22h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_11_21h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_11_22h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_11_23h2:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:*:*

History

13 Feb 2025, 17:16

Type Values Removed Values Added
Summary (en) This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with. (en) This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.

Information

Published : 2023-10-18 04:15

Updated : 2025-02-13 17:16


NVD link : CVE-2023-38545

Mitre link : CVE-2023-38545

CVE.ORG link : CVE-2023-38545


JSON object : View

Products Affected

netapp

  • active_iq_unified_manager
  • oncommand_workflow_automation
  • oncommand_insight

microsoft

  • windows_server_2022
  • windows_11_23h2
  • windows_10_21h2
  • windows_11_22h2
  • windows_10_1809
  • windows_11_21h2
  • windows_10_22h2
  • windows_server_2019

fedoraproject

  • fedora

haxx

  • libcurl
CWE
CWE-787

Out-of-bounds Write