Description
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.
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| clustered-data-ontap | — | — |
| curl | 7.71.0 | 7.84.0 |
| debian-linux | — | — |
| element-software | — | — |
| fedora | — | — |
| h300s-firmware | — | — |
| h410s-firmware | — | — |
| h500s-firmware | — | — |
| h700s-firmware | — | — |
| hci-management-node | — | — |
| macos | — | 13.0 |
| scalance-sc622-2c-firmware | — | 3.0 |
| scalance-sc626-2c-firmware | — | 3.0 |
| scalance-sc632-2c-firmware | — | 3.0 |
| scalance-sc636-2c-firmware | — | 3.0 |
| scalance-sc642-2c-firmware | — | 3.0 |
| scalance-sc646-2c-firmware | — | 3.0 |
| solidfire | — | — |
| universal-forwarder | — | — |
References
Similar Threats
- High CVE-2022-23241
- High CVE-2022-26377
- Medium CVE-2022-28614
- Critical CVE-2022-28615
- High CVE-2022-29404
Site Security Check
Concerned your site may already be targeted?
BotEraser analyzes incoming traffic patterns and helps identify bot behavior consistent with known exploit attempts.
Check My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.