← back
CVE-2023-38545highCWE-787

CVE-2023-38545

43Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 8.8epss 78%
exploitation probability
78%top 1% of all CVEs
observed exploitation
nono source reports it
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Fixed
12 products (253 components)
Red Hat Enterprise Linux BaseOS (v. 9) · Red Hat Enterprise Linux AppStream (v. 9) · Red Hat Enterprise Linux BaseOS EUS (v.9.0) · Red Hat Enterprise Linux AppStream EUS (v.9.0) · Satellite Client 6 for RHEL 7 · and others 7
Not affected
10 products (215 components)because the vulnerable code is not present in the product
Red Hat Satellite 6.14 for RHEL 8 · Red Hat JBoss Core Services on RHEL 8 · Red Hat JBoss Core Services on RHEL 7 Server · Satellite Client 6 for RHEL 7 · Red Hat Enterprise Linux 8 · and others 5
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
curl · curl