Buffer overflow in Curl

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.

Vulnerability class: Buffer Overflow

EPSS: 0.785 (99.6th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2023-38545?
CVE-2023-38545 is a critical-severity vulnerability in Curl, classified under Out-of-bounds Write. CVSS score: 9.8/10. Published 2023-10-18.
How severe is CVE-2023-38545?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2023-38545 known to be exploited?
32 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.