dbcve.org
CurlApplication · Haxx

CVE-2022-27780

HIGH · 7.5 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 7.83.1 or later.
See remediation →
84/100
Remediation priority · High
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
The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *different* URL usingthe wrong host name when it is later retrieved.For example, a URL like `http://example.com%2F127.0.0.1/`, would be allowed bythe parser and get transposed into `http://example.com/127.0.0.1/`. This flawcan be used to circumvent filters, checks and more.

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.80.0, < 7.83.1
Hci Bootstrap OsOperating system
Affected:all versions
Clustered Data OntapApplication
Affected:all versions
Solidfire\, Enterprise Sds \& Hci Storage NodeApplication
Affected:all versions
Solidfire \& Hci Management NodeApplication
Affected:all versions
H410s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating 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
None
Integrity
High
Availability
None

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

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

curl 7.83.1 or later

  1. Check current curl version using: curl --version or rpm -q curl / dpkg -l curl
  2. Download curl version 7.83.1 or later from the official curl website (curl.se) or your distribution's package repository
  3. For Linux systems using package managers: apt-get update && apt-get install curl (Debian/Ubuntu) or yum update curl (RHEL/CentOS)
  4. Verify the upgrade was successful by running: curl --version
  5. Ensure any applications or services using curl are restarted to pick up the new version
  6. Test that URL parsing now correctly rejects percent-encoded separators in the host portion
Caveat Minimal risk - this is a security fix that corrects URL parsing behavior; applications relying on the incorrect behavior should be fixed to use proper URL encoding

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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