VYPR
Unrated severityNVD Advisory· Published Feb 9, 2023· Updated Oct 27, 2024

CVE-2022-43552

CVE-2022-43552

Description

Use-after-free in curl <7.87.0 when HTTP proxy denies tunneling SMB or TELNET, causing heap-use-after-free in shutdown code path.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Use-after-free in curl <7.87.0 when HTTP proxy denies tunneling SMB or TELNET, causing heap-use-after-free in shutdown code path.

Vulnerability

A use-after-free vulnerability exists in curl versions prior to 7.87.0. The bug occurs in the transfer shutdown code path when an HTTP proxy denies a tunnel request for the SMB or TELNET protocols. When the proxy returns a denial, curl frees a heap-allocated struct but later continues to use it, leading to a use-after-free condition. All curl versions before 7.87.0 are affected [1][2].

Exploitation

An attacker would need to control an HTTP proxy that is used by curl. By configuring the proxy to deny tunnel operations for SMB or TELNET, the attacker can trigger the use-after-free when curl processes the denial during the shutdown phase. The attacker does not require authentication or write access to the target system; the network position to intercept or control the proxy response is sufficient [1][2].

Impact

Successful exploitation could lead to denial of service or potentially arbitrary code execution, as the heap-use-after-free may corrupt memory. The impact depends on the application using libcurl; in worst-case scenarios, an attacker could achieve remote code execution. However, the vendor notes that exploitation is limited to scenarios where an attacker can control the HTTP proxy response [1][2].

Mitigation

The vulnerability is fixed in curl version 7.87.0 and later. Users should upgrade to the latest version of curl (8.3.0-r2 or higher for Gentoo) [2]. For macOS Ventura, Apple addressed a related CVE-2023-32436 with improved bounds checks in macOS Ventura 13.3, but direct patch information for this specific CVE is not provided in the references. No workaround is available other than updating [1][2].

AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

43

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

5

News mentions

0

No linked articles in our index yet.