CVE-2022-27779 — libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided...
libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to receive and send cookies. curl's "cookie engine" can bebuilt with or without [Public Suffix List](https://publicsuffix.org/)awareness. If PSL support not provided, a more rudimentary check exists to atleast prevent cookies from being set on TLDs. This check was broken if thehost name in the URL uses a trailing dot.This can allow arbitrary sites to set cookies that then would get sent to adifferent and unrelated site or domain.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 2.7% (30-day exploitation probability)+13
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Haxx Curl, Netapp Clustered Data Ontap, Netapp H300s Firmware…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Haxx | Curl | ≥ 7.82.0 and < 7.83.1 | Vulnerable | NIST National Vulnerability Database |
| Netapp | Clustered Data Ontap | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Hci Bootstrap Os | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Hci Compute Node | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Solidfire & Hci Management Node | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Solidfire, Enterprise Sds & Hci Storage Node | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Splunk | Universal Forwarder | ≥ 8.2.0 and < 8.2.12≥ 9.0.0 and < 9.0.6version 9.1.0 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.3 | CVSS 3.1 | Medium | 3.9 | 1.4 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 5.0 | CVSS 2.0 | Medium | 10.0 | 2.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for anomalous data read/export volumes and access to sensitive records.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · haxx/curl, netapp/hci bootstrap os, netapp/clustered data ontap, netapp/solidfire, enterprise sds & hci storage node, ne
- CVSS changed · 5.3
- Source status changed · → Modified
- Record created in this database
- 2022
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
7 on the record
- hackerone.com/reports/1553301
- github.com/advisories/GHSA-r5c3-3mf2-x8c7
- security.gentoo.org/glsa/202212-01
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- security.netapp.com/advisory/ntap-20220609-0009
- security.netapp.com/advisory/ntap-20220609-0009/
- nvd.nist.gov/vuln/detail/CVE-2022-27779
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-82209 Insertion of Sensitive Information Into Sent Data in Haxx Curl Sep 6, 2026
- High CVE-2026-80229 Use After Free in Haxx Curl Sep 6, 2026
- High CVE-2026-80230 Improper Certificate Validation in Haxx Curl Sep 6, 2026
- High CVE-2026-80231 A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup for a given… Sep 6, 2026
- High CVE-2026-82208 Improper Certificate Validation in Haxx Curl Sep 6, 2026
- High CVE-2026-80255 Insertion of Sensitive Information Into Sent Data in Haxx Curl Sep 6, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-27779 is "libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided...", rated Medium. It affects Curl (Haxx); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 2.73% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.