dbcve.org
CurlApplication · Haxx

CVE-2022-32207

CRITICAL · 9.8 CVSS v3.1 Published 2022-07-07
Fix available
A fix is available. Upgrade to 7.84.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally *widen* the permissions for the target file, leaving the updated file accessible to more users than intended.

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

A detailed technical summary for this CVE is being prepared.

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.69.0, < 7.84.0
FedoraOperating system
Affected:= 35
Debian LinuxOperating system
Affected:= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 on the system using: curl --version
  2. For Debian/Ubuntu systems: Run 'sudo apt-get update && sudo apt-get install curl' to upgrade to the latest available version
  3. For RHEL/Fedora systems: Run 'sudo dnf update curl' or 'sudo yum update curl'
  4. For systems with manual curl installation: Download curl 7.84.0 or later from the official curl website (curl.se) and recompile/install
  5. Verify the upgrade was successful by running: curl --version and confirm the version is 7.84.0 or higher
  6. For NetApp products (Clustered Data ONTAP, Element Software, HCI Management Node, Solidfire, Bootstrap OS): Apply the appropriate patch or update as specified in NetApp's security advisory on their support site
Caveat Review curl 7.84.0 release notes for any behavioral changes, deprecations, or API changes that might affect existing scripts or integrations

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 $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-32207 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