# CVE-2023-45290: Memory exhaustion in multipart form parsing in net/textproto and net/http > Attackers can cause memory exhaustion and denial of service by sending maliciously crafted multipart form data with very long lines to Go applications. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Mar 2024 - **Updated:** 13 Feb 2025 - **Also known as:** ALSA-2024:3830, ALSA-2024:3831, AZL-37493, AZL-37504, AZL-79032, AZL-98844, BELL-CVE-2023-45290, BIT-golang-2023-45290, DEBIAN-CVE-2023-45290, GHSA-rr6r-cfgf-gc6h, GO-2024-2599, MINI-h3mh-xwrq-9xw8, MINI-m82j-fc3m-mjr8, MINI-mff7-r4wp-vpx5, RHSA-2024:3830, RHSA-2024:3831, RLSA-2024:3830, UBUNTU-CVE-2023-45290 ## What is CVE-2023-45290? CVE-2023-45290 is a medium-severity denial of service vulnerability in Go standard library net/textproto, published on 5 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description When parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue, Request.PostFormValue, or Request.FormFile), limits on the total size of the parsed form were not applied to the memory consumed while reading a single form line. This permits a maliciously crafted input containing very long lines to cause allocation of arbitrarily large amounts of memory, potentially leading to memory exhaustion. With fix, the ParseMultipartForm function now correctly limits the maximum size of form lines. Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling) ## Which versions are affected by CVE-2023-45290? 2 open source packages ship an affected version, including golang and stdlib. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `golang` | Bitnami | All versions | 1.21.8, 1.22.1 | | `stdlib` | Go | All versions | 1.21.8, 1.22.1 | | `containernetworking-plugins` | AlmaLinux:9 | All versions | 1:1.4.0-3.el9_4 | | `gvisor-tap-vsock` | AlmaLinux:9 | All versions | 6:0.7.3-3.el9_4.alma.1 | | `containernetworking-plugins` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.4.0-3.el9_4 | | `containernetworking-plugins-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.4.0-3.el9_4 | | `containernetworking-plugins-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 1:1.4.0-3.el9_4 | | `gvisor-tap-vsock` | Red Hat:enterprise_linux:9::appstream | All versions | 6:0.7.3-3.el9_4 | | `gvisor-tap-vsock-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 6:0.7.3-3.el9_4 | | `gvisor-tap-vsock-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 6:0.7.3-3.el9_4 | | `gvisor-tap-vsock` | Rocky Linux:9 | All versions | 6:0.7.3-3.el9_4 | ## How do I fix CVE-2023-45290? Upgrade golang to a fixed version for your release line: 1.21.8 or 1.22.1. ## Is CVE-2023-45290 being exploited? There is no known exploitation of CVE-2023-45290 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-45290 and fix it if it is affected. What it is: CVE-2023-45290 is a medium-severity denial of service vulnerability in Go standard library net/textproto, published on 5 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-45290 in the wild and no public exploit code. Affected packages and fixed versions: - golang (Bitnami): affected all versions; fixed in 1.21.8, 1.22.1 - stdlib (Go): affected all versions; fixed in 1.21.8, 1.22.1 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-45290/ (Markdown: https://insights.sbomify.com/CVE-2023-45290/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45290 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45290 - OSV: https://osv.dev/vulnerability/CVE-2023-45290 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-45290/ Summaries are generated and may contain mistakes; the official description above is the record.