# CVE-2023-24534: Excessive memory allocation in net/http and net/textproto

> An attacker can cause memory exhaustion and denial of service in Go applications by sending crafted HTTP or MIME headers that trigger excessive memory allocation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 6 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** AZL-25990, AZL-26027, AZL-37414, AZL-37484, AZL-52878, AZL-79066, AZL-98766, BIT-golang-2023-24534, DEBIAN-CVE-2023-24534, GHSA-8v5j-pwr7-w5f8, GO-2023-1704, MINI-hvrm-hh7q-vg33, OESA-2023-1822, OESA-2023-1823, OESA-2023-1824, UBUNTU-CVE-2023-24534

## What is CVE-2023-24534?

CVE-2023-24534 is a high-severity denial of service vulnerability in Golang Go, published on 6 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including golang and stdlib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `golang` | Bitnami | All versions | 1.19.8, 1.20.3 |
| `stdlib` | Go | All versions | 1.19.8, 1.20.3 |

Products: Golang Go.

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

Upgrade golang to a fixed version for your release line: 1.19.8 or 1.20.3.

## Is CVE-2023-24534 being exploited?

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

## Other vulnerabilities in Golang Go

- [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild)
- [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8)
- [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8)
- [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8)
- [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-24534 is a high-severity denial of service vulnerability in Golang Go, published on 6 Apr 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-2023-24534 in the wild and no public exploit code.

Affected packages and fixed versions:
- golang (Bitnami): affected all versions; fixed in 1.19.8, 1.20.3
- stdlib (Go): affected all versions; fixed in 1.19.8, 1.20.3

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

## Sources

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

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