A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set super cookies that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.
Weakness
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Curl | Haxx | 7.46.0 (including) | 8.21.0 (excluding) |
| Red Hat Enterprise Linux 10 | RedHat | curl-0:8.12.1-4.el10_2.6 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | curl-0:8.12.1-1.el10_0.10 | * |
| Red Hat Enterprise Linux 9 | RedHat | curl-0:7.76.1-40.el9_8.8 | * |
| Red Hat Enterprise Linux 9 | RedHat | curl-0:7.76.1-40.el9_8.8 | * |
| Red Hat JBoss Core Services 2.4.62.SP5 | RedHat | * | |
| Red Hat Cost Management On-Premise 1 | RedHat | costmanagement/costmanagement-ui-rhel10:1791460851 | * |
| Red Hat Hardened Images | RedHat | curl-main-8.21.0-0.1.hum1 | * |
| Red Hat Hardened Images | RedHat | rust-main-1.96.1-1.hum1 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/cds-kubernetes-rhel9:1791978534 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/cds-rhel9:1791978528 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/haproxy-rhel9:1791978528 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/installer-rhel9:1791964013 | * |
| Red Hat Update Infrastructure 5 | RedHat | rhui5/rhua-rhel9:1791978693 | * |
| Curl | Ubuntu | esm-infra-legacy/xenial | * |
| Curl | Ubuntu | esm-infra/bionic | * |
| Curl | Ubuntu | esm-infra/focal | * |
| Curl | Ubuntu | jammy | * |
| Curl | Ubuntu | noble | * |
| Curl | Ubuntu | questing | * |
| Curl | Ubuntu | resolute | * |
| Curl | Ubuntu | upstream | * |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/12.html
- https://cwe.mitre.org/data/definitions/217.html
- https://cwe.mitre.org/data/definitions/612.html
- https://cwe.mitre.org/data/definitions/613.html
- https://cwe.mitre.org/data/definitions/618.html
- https://cwe.mitre.org/data/definitions/619.html
- https://cwe.mitre.org/data/definitions/621.html
- https://cwe.mitre.org/data/definitions/622.html
- https://cwe.mitre.org/data/definitions/623.html