# CVE-2022-43552: Use after free in https://github.com/curl/curl > A use-after-free flaw in curl allows attackers to cause crashes or potentially execute code when tunneling SMB or TELNET through a proxy. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Feb 2023 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2022-43552, AZL-13280, AZL-13284, AZL-13287, AZL-13289, AZL-34604, AZL-37981, CLEANSTART-2026-EB72935, CLSA-2023-1678820199, CURL-CVE-2022-43552, DEBIAN-CVE-2022-43552, GHSA-6342-4x32-pp8v, JLSEC-2026-401, OESA-2023-1005, OESA-2023-1006, RHSA-2023:7743, SUSE-SU-2022:4598-1, SUSE-SU-2022:4633-1, UBUNTU-CVE-2022-43552 ## What is CVE-2022-43552? CVE-2022-43552 is a medium-severity use after free vulnerability in Apple Macos, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2022-43552? It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `curl` | Red Hat:enterprise_linux:7::client | All versions | 0:7.29.0-59.el7_9.2 | | `curl-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl` | Red Hat:enterprise_linux:7::client | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:7.29.0-59.el7_9.2 | | `curl-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:7.29.0-59.el7_9.2 | | `curl` | Red Hat:enterprise_linux:7::server | All versions | 0:7.29.0-59.el7_9.2 | | `curl-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl` | Red Hat:enterprise_linux:7::server | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:7.29.0-59.el7_9.2 | | `curl` | Red Hat:enterprise_linux:7::workstation | All versions | 0:7.29.0-59.el7_9.2 | | `curl-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl` | Red Hat:enterprise_linux:7::workstation | All versions | 0:7.29.0-59.el7_9.2 | | `libcurl-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:7.29.0-59.el7_9.2 | | `curl` | SUSE:Linux Enterprise Micro 5.1 | All versions | 7.66.0-150200.4.45.1 | | `curl` | SUSE:Linux Enterprise Micro 5.2 | All versions | 7.66.0-150200.4.45.1 | | `curl` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 7.66.0-150200.4.45.1 | | `curl` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 7.60.0-11.52.1 | | `curl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 7.60.0-11.52.1 | | `curl` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 7.60.0-11.52.1 | | `curl` | openSUSE:Leap 15.3 | All versions | 7.66.0-150200.4.45.1 | | `curl` | openSUSE:Leap Micro 5.2 | All versions | 7.66.0-150200.4.45.1 | Products: Apple Macos, Haxx Curl, Splunk Universal Forwarder. ## How do I fix CVE-2022-43552? Upgrade to a fixed version. ## Is CVE-2022-43552 being exploited? There is no known exploitation of CVE-2022-43552 in the wild and no public exploit code. ## Other vulnerabilities in Apple Macos - [CVE-2026-65400](https://insights.sbomify.com/CVE-2026-65400/): Apple macOS Improper Authentication (critical 9.8, exploited in the wild) - [CVE-2024-44146](https://insights.sbomify.com/CVE-2024-44146/): Security feature bypass in macOS (critical 10.0) - [CVE-2024-44148](https://insights.sbomify.com/CVE-2024-44148/): Security feature bypass in macOS (critical 10.0) - [CVE-2023-38586](https://insights.sbomify.com/CVE-2023-38586/): Security feature bypass in macOS (critical 10.0) - [CVE-2023-40455](https://insights.sbomify.com/CVE-2023-40455/): Security feature bypass in macOS (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-43552 and fix it if it is affected. What it is: CVE-2022-43552 is a medium-severity use after free vulnerability in Apple Macos, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-43552 in the wild and no public exploit code. Affected product: Apple Macos. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-43552/ (Markdown: https://insights.sbomify.com/CVE-2022-43552/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-43552 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-43552 - OSV: https://osv.dev/vulnerability/CVE-2022-43552 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-43552/ Summaries are generated and may contain mistakes; the official description above is the record.