Curl
secure cookie attribute bypass with tab
A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CISA ADP · CWE-201
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
curl curl
- >= 8.13.0, < 8.14.2
- >= 8.15.0, < 8.16.1
- >= 8.17.0, < 8.20.1
- >= 8.21.0, < 8.22.0
Fixed in 8.14.2, 8.16.1, 8.20.1, 8.22.0
curl curl
- >= 1aea05a6c2699e80c75936d58569851555acd603, < 4f6aa41a0145e930e766775dbe860883d350aa0a
Fixed in 4f6aa41a0145e930e766775dbe860883d350aa0a
curl curl
- 8.21.0
- 8.20.0
- 8.19.0
- 8.18.0
- 8.17.0
- 8.16.0
- 8.15.0
- 8.14.1
- 8.14.0
- 8.13.0
Mitigation
Upgrade curl to 8.14.2 or 8.16.1 or 8.20.1 or 8.22.0 or later.
Upgrade curl to 4f6aa41a0145e930e766775dbe860883d350aa0a or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.