QID 379552

QID 379552: Curl HTTP/2 Push Headers Memory-leak Vulnerability

If an application instructs libcurl to permit HTTP/2 server push and the number of received headers exceeds the maximum limit of 1000, libcurl terminates the server push but fails to release all previously allocated headers, resulting in memory leakage, which goes unnoticed by the application due to the silent failure of this error condition.

Affected Versions:
All Curl versions after 7.44.0 (including 7.44.0) and prior to version 8.7.0

QID Detection Logic (Windows Authenticated):
This QID checks for vulnerable version of curl by checking the fileversion of curl.exe. Please note that this QID checks for the curl.exe file at the default installation directory only.

QID Detection Logic (Mac OS Authenticated):
This QID checks for vulnerable version of curl on MacOS by checking the installed packages.

This vulnerability in libcurl could lead to memory leaks and potential resource exhaustion, impacting the stability and performance of applications relying on HTTP/2 server push functionality.

CVSS V3 rated as High - 7.5 severity.

CVSS V2 rated as Medium - 5 severity.

Solution

Vendor has released patch addressing the vulnerability. For more information, please refer to the Curl Security Advisory

Vendor References

Curl Security Advisory - curl.se/docs/CVE-2024-2398.html

CVEs related to QID 379552

CVE-2024-2398 |

Software Advisories

Advisory ID	Software	Component	Link
Curl Security Advisory			curl.se/docs/CVE-2024-2398.html

By selecting these links, you may be leaving CVEreport webspace. We have provided these links to other websites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose. CVEreport does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, CVEreport does not endorse any commercial products that may be mentioned on these sites. Please address comments about any linked pages to [email protected].