When curl retrieves an HTTP response, it stores the incoming headers so that
they can be accessed later via the libcurl headers API.
However, curl did not have a limit in how many or how large headers it would
accept in a response, allowing a malicious server to stream an endless series
of headers and eventually cause curl to run out of heap memory.
[
{
"vendor": "curl",
"product": "curl",
"versions": [
{
"version": "8.3.0",
"status": "affected",
"lessThan": "8.3.0",
"versionType": "semver"
},
{
"version": "7.84.0",
"status": "unaffected",
"lessThan": "7.84.0",
"versionType": "semver"
}
]
}
]
seclists.org/fulldisclosure/2023/Oct/17
seclists.org/fulldisclosure/2024/Jan/34
seclists.org/fulldisclosure/2024/Jan/37
seclists.org/fulldisclosure/2024/Jan/38
hackerone.com/reports/2072338
lists.fedoraproject.org/archives/list/[email protected]/message/5DCZMYODALBLVOXVJEN2LF2MLANEYL4F/
lists.fedoraproject.org/archives/list/[email protected]/message/M6KGKB2JNZVT276JYSKI6FV2VFJUGDOJ/
lists.fedoraproject.org/archives/list/[email protected]/message/TEAWTYHC3RT6ZRS5OZRHLAIENVN6CCIS/
security.gentoo.org/glsa/202310-12
security.netapp.com/advisory/ntap-20231013-0005/
support.apple.com/kb/HT214036
support.apple.com/kb/HT214057
support.apple.com/kb/HT214058
support.apple.com/kb/HT214063
www.insyde.com/security-pledge/SA-2023064