Skip to content
Noroxi
CVE-2022-32205· NVD / CVE Program· CNA hackerone

A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them.

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 31.4% (FIRST EPSS); higher than 98.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: curl (Alpine:v3.13) 7.79.1-r2; curl (Alpine:v3.15) 7.80.0-r2; curl (Alpine:v3.16) 7.83.1-r2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to curl (Alpine:v3.13) 7.79.1-r2; curl (Alpine:v3.15) 7.80.0-r2; curl (Alpine:v3.16) 7.83.1-r2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on `foo.example.com` can set cookies that also would match for `bar.example.com`, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.

MediumCVSS 4.3 · v3.1—No exploit Fix available
Published
Jul 7, 2022
Updated
Oct 14, 2026
EPSS
31.4% · 98th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
9 / 30 · 31.4%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.3
CNA · hackerone
4.3
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-32205

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
haxxcurl
fedoraprojectfedora
debiandebian linux
netappclustered data ontap
netappelement software
netapphci management node
netappsolidfire
netapph300s
netapph300s firmware
netapph500s
netapph500s firmware
netapph700s

and 17 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apple macosbefore 13.0
  • debian debian linux11.0
  • fedoraproject fedora35
  • haxx curl7.71.0 and later · before 7.84.0
  • netapp clustered data ontapall versions
  • netapp element softwareall versions
  • netapp h300s firmwareall versions
  • netapp h410s firmwareall versions
  • netapp h500s firmwareall versions
  • netapp h700s firmwareall versions
  • netapp hci management nodeall versions
  • netapp solidfireall versions
  • siemens scalance sc622-2c firmwarebefore 3.0
  • siemens scalance sc626-2c firmwarebefore 3.0
  • siemens scalance sc632-2c firmwarebefore 3.0
  • siemens scalance sc636-2c firmwarebefore 3.0
  • siemens scalance sc642-2c firmwarebefore 3.0
  • siemens scalance sc646-2c firmwarebefore 3.0
  • splunk universal forwarder8.2.0 and later · before 8.2.12
  • splunk universal forwarder9.0.0 and later · before 9.0.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a https://github.com/curl/curl

    • Fixed in 7.84.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.13curlfrom 7.71.0 · before 7.79.1-r27.79.1-r2
Alpine:v3.15curlfrom 7.71.0 · before 7.80.0-r27.80.0-r2
Alpine:v3.16curlfrom 7.71.0 · before 7.83.1-r27.83.1-r2
Alpine:v3.17curlfrom 7.71.0 · before 7.84.0-r07.84.0-r0
Debian:11curlbefore 7.74.0-1.3+deb11u27.74.0-1.3+deb11u2
Debian:12curlbefore 7.84.0-17.84.0-1
openSUSE:Leap 15.4curlbefore 7.79.1-150400.5.3.17.79.1-150400.5.3.1
openSUSE:Tumbleweedcurlbefore 7.84.0-1.17.84.0-1.1
SUSE:Linux Enterprise Module for Basesystem 15 SP4curlbefore 7.79.1-150400.5.3.17.79.1-150400.5.3.1

Same product

haxx: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
    51Plan
  • CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
    47Plan
  • CVE-2024-2398HTTP/2 push headers memory-leak
    45Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-27782Jun 2, 2022 · libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.
    31Monitor
  • ← EarlierCVE-2022-30115Jun 2, 2022 · Using its HSTS support, curl can be instructed to use HTTPS directly insteadof using an insecure clear-text HTTP step even when HTTP is prov
    17Monitor
  • Later →CVE-2022-32206Jul 7, 2022 · curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:curl7.79.1-r2 · Alpine:v3.13Package registry (OSV)
debian:curl7.84.0-1 · Debian:12Package registry (OSV)
opensuse:curl7.79.1-150400.5.3.1 · openSUSE:Leap 15.4Package registry (OSV)
suse:curl7.79.1-150400.5.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

CVSS vector

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

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records