CurlApplication · Haxx

CVE-2022-32206

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-07
Fix available
A fix is available. Upgrade to 7.84.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Public exploit Remotely reachable No privileges Patch available

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
curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

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
How this class of weakness works · CWE-770

The application allocates memory, connections, or handles in response to a request without enforcing any cap, so a modest amount of malicious traffic exhausts the resource and denies service to everyone else. The fix is enforcing quotas, limits, and timeouts on what any single request or client can consume.

General guidance for the resource allocation without limits class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
CurlApplication
Affected:< 7.84.0
FedoraOperating system
Affected:= 35
Debian LinuxOperating system
Affected:= 10.0= 11.0
Clustered Data OntapApplication
Affected:all versions
Element SoftwareApplication
Affected:all versions
Hci Management NodeApplication
Affected:all versions
SolidfireApplication
Affected:all versions
Bootstrap OsOperating system
Affected:all versions

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

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

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 7.84.0 or later
Fixed in 7.84.0
Recommended fix High confidence

curl >= 7.84.0

  1. Identify the curl version currently installed: curl --version or apt list --installed 2>/dev/null | grep curl
  2. Upgrade curl to version 7.84.0 or later. On Linux distributions, use: apt-get update && apt-get install curl (Debian/Ubuntu) or yum/dnf update curl (RHEL/Fedora)
  3. Verify the upgrade was successful by checking curl --version to ensure the version is >= 7.84.0
  4. For affected NetApp products (Clustered Data ONTAP, Element Software, HCI Management Node, Solidfire), apply the appropriate vendor patch from https://cert-portal.siemens.com/productcert/pdf/ssa-333517.pdf or contact NetApp support for product-specific updates
  5. For Fedora 35, apply available system updates: dnf update curl
Caveat This is a security fix upgrading to a stable release; minimal risk of breaking changes expected. However, test in non-production environment first if concerned about compatibility with custom scripts using curl's decompression behavior.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32206 — 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-32206 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