ghsa-99j9-jf36-9747
Vulnerability from github
Published
2023-09-15 06:30
Modified
2024-04-01 18:30
Severity ?
Details
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.
{ affected: [], aliases: [ "CVE-2023-38039", ], database_specific: { cwe_ids: [ "CWE-770", ], github_reviewed: false, github_reviewed_at: null, nvd_published_at: "2023-09-15T04:15:10Z", severity: "HIGH", }, details: "When curl retrieves an HTTP response, it stores the incoming headers so that\nthey can be accessed later via the libcurl headers API.\n\nHowever, curl did not have a limit in how many or how large headers it would\naccept in a response, allowing a malicious server to stream an endless series\nof headers and eventually cause curl to run out of heap memory.", id: "GHSA-99j9-jf36-9747", modified: "2024-04-01T18:30:55Z", published: "2023-09-15T06:30:18Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2023-38039", }, { type: "WEB", url: "https://hackerone.com/reports/2072338", }, { type: "WEB", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5DCZMYODALBLVOXVJEN2LF2MLANEYL4F", }, { type: "WEB", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/M6KGKB2JNZVT276JYSKI6FV2VFJUGDOJ", }, { type: "WEB", url: "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TEAWTYHC3RT6ZRS5OZRHLAIENVN6CCIS", }, { type: "WEB", url: "https://security.gentoo.org/glsa/202310-12", }, { type: "WEB", url: "https://security.netapp.com/advisory/ntap-20231013-0005", }, { type: "WEB", url: "https://support.apple.com/kb/HT214036", }, { type: "WEB", url: "https://support.apple.com/kb/HT214057", }, { type: "WEB", url: "https://support.apple.com/kb/HT214058", }, { type: "WEB", url: "https://support.apple.com/kb/HT214063", }, { type: "WEB", url: "https://www.insyde.com/security-pledge/SA-2023064", }, { type: "WEB", url: "http://seclists.org/fulldisclosure/2023/Oct/17", }, { type: "WEB", url: "http://seclists.org/fulldisclosure/2024/Jan/34", }, { type: "WEB", url: "http://seclists.org/fulldisclosure/2024/Jan/37", }, { type: "WEB", url: "http://seclists.org/fulldisclosure/2024/Jan/38", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", type: "CVSS_V3", }, ], }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.