# CVE-2023-32001: We issued this CVE pre-maturely, as we have subsequently realized that this issue points out a problem that there really is no safe measures


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Jul 2023
- **Updated:** 27 Aug 2023
- **Also known as:** GHSA-xc3w-ghxg-pw5f, OESA-2023-1443, SUSE-SU-2023:2880-1, SUSE-SU-2023:2891-1, openSUSE-SU-2024:13069-1

## What is CVE-2023-32001?

CVE-2023-32001 is a vulnerability in curl, published on 26 Jul 2023. 

### Official description

We issued this CVE pre-maturely, as we have subsequently realized that this issue points out a problem that there really is no safe measures around or protections for.

## Which versions are affected by CVE-2023-32001?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curl` | SUSE:Linux Enterprise Micro 5.3 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | SUSE:Linux Enterprise Micro 5.4 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 8.0.1-11.68.1 |
| `curl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 8.0.1-11.68.1 |
| `curl` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 8.0.1-11.68.1 |
| `curl` | openSUSE:Leap 15.4 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | openSUSE:Leap 15.5 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | openSUSE:Leap Micro 5.3 | All versions | 8.0.1-150400.5.26.1 |
| `curl` | openSUSE:Tumbleweed | All versions | 8.2.0-1.1 |

## How do I fix CVE-2023-32001?

Upgrade to a fixed version.

## Is CVE-2023-32001 being exploited?

There is no known exploitation of CVE-2023-32001 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32001 and fix it if it is affected.

What it is: CVE-2023-32001 is a vulnerability in curl, published on 26 Jul 2023. 
Exploitation: There is no known exploitation of CVE-2023-32001 in the wild and no public exploit code.

Affected product: curl. 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-2023-32001/ (Markdown: https://insights.sbomify.com/CVE-2023-32001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32001
- OSV: https://osv.dev/vulnerability/CVE-2023-32001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-32001/
Summaries are generated and may contain mistakes; the official description above is the record.