dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2023-45290

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Go's net/http package, the multipart form parser (used by Request.ParseMultipartForm and related methods like Request.FormValue) failed to apply size limits to individual form lines. This allowed attackers sending specially crafted multipart forms with extremely long lines to trigger unbounded memory allocation, potentially exhausting server resources.

MitigationUpgrade Go to a version that includes the fix (Go 1.21.8 or later for Go 1.21, Go 1.22.1 or later for Go 1.22). Review applications using multipart form parsing and consider implementing additional application-layer size limits as defense-in-depth.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the Go runtime version
    Run 'go version' to identify the installed Go version. If using a container or packaged application, check the version bundled with that artifact.
    Affected if The installed Go version is below 1.21.8 (for the 1.21 branch) or below 1.22.1 (for the 1.22 branch).
  2. Identify applications using multipart form parsing
    Search source code for calls to Request.ParseMultipartForm, Request.FormValue, Request.PostForm, or Request.FormFile methods. These indicate multipart form handling.
    Affected if The application code contains any of these multipart form parsing methods and is running on a vulnerable Go version.
  3. Check for external Go dependencies that may include net/http
    Review go.mod and any vendored dependencies to confirm no third-party packages are bundling a separate copy of the net/http package.
    Affected if A vendored or embedded copy of net/http exists with an older version than the main Go runtime.
  4. Identify internet-facing services using multipart upload
    Review server configurations and HTTP handler implementations that accept multipart/form-data requests, such as file upload endpoints or API endpoints accepting form data.
    Affected if The service accepts multipart form submissions from clients and runs on a vulnerable Go version.

You are affected if your Go runtime version is below 1.21.8 or 1.22.1 and your application uses any multipart form parsing functionality via net/http.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Go to a version that includes the fix (Go 1.21.8 or later for Go 1.21, Go 1.22.1 or later for Go 1.22). Review applications using multipart form parsing and consider implementing additional application-layer size limits as defense-in-depth.

Recommended fix High confidence

Go 1.21.7 or later / Go 1.22.0 or later

  1. Check current Go version by running: go version
  2. Upgrade Go to version 1.21.7 or later, or version 1.22.0 or later
  3. For Linux/macOS: Use the official Go installation method (download from go.dev/dl or use version manager like gvm/gotenvy)
  4. For Windows: Download installer from go.dev/dl or use choco install golang
  5. Verify upgrade successful: go version
  6. Rebuild any applications that handle multipart form uploads to ensure they use the fixed Go runtime
Caveat Minor Go version upgrades typically have few breaking changes; verify any application behavior changes in release notes if concerned

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45290 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45290 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data