LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32206: curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compress...

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a denial-of-service flaw in curl before 7.84.0. A malicious server could send an overly complex compressed HTTP response that makes curl allocate excessive heap memory or fail with out-of-memory errors. The known impact is availability, not data theft or tampering.

Executive priority

Treat as a routine but necessary availability-risk patch. Prioritize internet-facing services, automation, and products that use curl to fetch external content, especially where outages or memory exhaustion would affect customers or operations.

Technical view

curl accepted unbounded chained HTTP content-encoding decompression steps. An attacker-controlled server response could trigger excessive memory allocation during decompression, a CWE-770 resource-allocation issue. The CVSS vector is network reachable with low attack complexity but requires the client or user workflow to request the malicious server.

Likely exposure

Exposure is most likely where curl or libcurl before 7.84.0 fetches HTTP content from untrusted or attacker-controlled servers. Also check operating systems, containers, appliances, and products that bundle libcurl, including vendor-maintained backports.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Practical exploitation depends on a vulnerable curl client receiving a malicious compressed response from a server it contacts.

Researcher notes

The issue is bounded to availability: CVSS reports no confidentiality or integrity impact. The affected record names curl before 7.84.0 and describes the fix version, but source details do not provide a standalone workaround beyond vendor updates and guidance.

Mitigation direction

  • Upgrade curl and libcurl to 7.84.0 or a vendor-patched package.
  • Apply OS and product security updates from Debian, Fedora, Gentoo, Apple, NetApp, or Siemens where applicable.
  • Inventory containers, appliances, and statically linked applications that may bundle libcurl.
  • If immediate upgrade is blocked, check vendor guidance for supported compensating controls.

Validation and detection

  • Check installed curl and libcurl versions against 7.84.0 or vendor backport advisories.
  • Confirm package changelogs include CVE-2022-32206 remediation, not only a higher version string.
  • Review SBOMs and container images for embedded or statically linked libcurl.
  • Identify workflows that fetch untrusted URLs or third-party HTTP content.
  • Verify vendor advisories for affected downstream products in your estate.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-32206 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-32206Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ahttps://github.com/curl/curlFixed in 7.84.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.