tornado is vulnerable to Denial of Service (DoS)
75
High Risk
CurlAsyncHTTPClient buffers and decompresses a response body with no upper limit, so a server that returns a highly compressed body can expand it to far more data than the wire size and exhaust the client process's memory. This applies whether or not a streaming_callback is used, since both the buffered write path and the streaming write path accepted chunks unconditionally. The fix adds a max_body_size argument, tracked against the decompressed size, that pauses and then fails the transfer once the limit is reached.
You are affected if you are using a version that falls within the vulnerable range and configure AsyncHTTPClient to use CurlAsyncHTTPClient to fetch responses from servers you do not fully trust.
tornado is vulnerable to Denial of Service (DoS) in versions 0.2 - 6.5.8.
Upgrade the tornado library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.