TextApplication · Golang

CVE-2022-32149

HIGH · 7.5 CVSS v3.1 Published 2022-10-14
Fix available
A fix is available. Upgrade to 0.3.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An attacker may cause a denial of service by crafting an Accept-Language header which ParseAcceptLanguage will take significant time to parse.

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 · moderate confidence

The ParseAcceptLanguage function can be exploited via specially crafted Accept-Language HTTP headers that cause the parser to consume excessive CPU time, leading to denial of service.

MitigationImplement input validation, length limits, or parsing timeouts on Accept-Language headers; otherwise upgrade to a patched version if the library is identified.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TextApplication
Affected:< 0.3.8

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify golang.org/x/text usage
    Search your codebase (go.mod, go.sum) for 'golang.org/x/text' dependency and note its version
    Affected if The installed version is lower than 0.3.8
  2. Locate ParseAcceptLanguage calls
    Search your codebase for imports of 'golang.org/x/text/language' and usages of 'ParseAcceptLanguage' function
    Affected if Code directly calls ParseAcceptLanguage to parse Accept-Language headers
  3. Check for input validation
    Inspect the code paths that handle Accept-Language HTTP headers; look for length limits, validation, or timeouts applied before calling ParseAcceptLanguage
    Affected if Accept-Language headers are passed to ParseAcceptLanguage without prior validation or limits

You are affected if your project uses golang.org/x/text version below 0.3.8 and processes unvalidated Accept-Language headers via ParseAcceptLanguage.

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
Upgrade available Upgrade to 0.3.8 or later
Fixed in 0.3.8
Interim mitigation

Implement input validation, length limits, or parsing timeouts on Accept-Language headers; otherwise upgrade to a patched version if the library is identified.

Recommended fix High confidence

golang.org/x/text v0.3.8

  1. Identify all Go modules that depend on the 'golang.org/x/text' package by running 'go list -m all' or inspecting go.mod files
  2. Run 'go get golang.org/x/[email protected]' to upgrade the text package to the fixed version
  3. Run 'go mod tidy' to clean up dependencies and update go.mod/go.sum files
  4. Rebuild and redeploy the application to include the patched library

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

Fix this in Text Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2022-32149 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