HTTP applications (servers) based on Crow through 1.0+4 may allow a Use-After-Free and code execution when HTTP pipelining is used. The HTTP parser supports HTTP pipelining, but the asynchronous Connection layer is unaware of HTTP pipelining. Specifically, the Connection layer is unaware that it has begun processing a later request before it has finished processing an earlier request.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://cwe.mitre.org/data/definitions/372.html | third party advisory technical description |
| https://github.com/CrowCpp/Crow/pull/524 | third party advisory patch |
| https://github.com/0xhebi/CVEs/blob/main/Crow/CVE-2022-38667.md | third party advisory exploit |
| https://gynvael.coldwind.pl/?id=753 | third party advisory exploit |