Security readout for executives and security teams
Plain-English summary
This issue lets a malicious web server make vulnerable curl clients keep too many large cookies. Later requests can become too large for curl’s own safety limit and fail, causing a limited denial of service until the cookies expire or are cleared.
Executive priority
Treat this as a moderate availability risk, not a data-theft issue. Prioritize internet-facing automation, managed devices, and products that bundle curl, especially where failed HTTP requests could disrupt business processes.
Technical view
curl before 7.84.0 stored excessive Set-Cookie headers. Large retained cookies could push later matching HTTP requests over curl’s 1,048,576-byte request-size threshold, returning errors. Cookie domain matching can affect sibling subdomains under the same registrable domain.
Likely exposure
Exposure is most likely in systems, scripts, appliances, or applications using curl or libcurl before 7.84.0 while retaining cookies from untrusted or semi-trusted HTTP servers.
Exploitation context
The bundle reports CVSS 4.3 with network attack vector, low complexity, no privileges, and required user interaction. It is not listed as CISA KEV, and the provided sources do not establish active exploitation.
Researcher notes
The key exposure condition is persistent cookie handling before curl 7.84.0. The denial can extend across sibling subdomains because cookie matching may carry attacker-set cookies to another host under the same second-level domain.
Mitigation direction
- Upgrade curl or libcurl to 7.84.0 or a vendor-fixed backport.
- Apply operating system or product advisories from relevant vendors.
- Clear retained cookie stores for affected workflows after patching.
- Review vendor guidance for embedded, appliance, or bundled curl deployments.
Validation and detection
- Inventory curl and libcurl versions across hosts, containers, and appliances.
- Confirm vendor packages include the CVE-2022-32205 fix or backport.
- Identify workflows that retain cookies from untrusted HTTP endpoints.
- Check for repeated curl request-size errors or unexplained availability failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2022-32205 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (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:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/1569946CVE reference
- FEDORA-2022-1b3d7f6973CVE reference · vendor-advisory
- DSA-5197CVE reference · vendor-advisory
- https://security.netapp.com/advisory/ntap-20220915-0003/CVE reference
- https://support.apple.com/kb/HT213488CVE reference
- https://cert-portal.siemens.com/productcert/pdf/ssa-333517.pdfCVE reference
- GLSA-202212-01CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.