Skip to main content
VulnerabilityPublished Updated

CVE-2024-58384: Snakeviz · Tornado has a CRLF injection in CurlAsyncHTTPClient headers

Affects snakevizSource GCVE Database

0
Compare
Authoritative record:CVE-2024-58384· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.2.0_1 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0_1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade snakeviz to 2.2.0_1.

Affected software

ProductAffectedFixed in
Homebrewsnakevizpkg:brew/snakevizOther threatsAffected
  • >=2.2.0 <2.2.0_1
Fixed in
  • 2.2.0_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Tornado version 2.2.0_1 that addresses this vulnerability. Users should upgrade to version 2.2.0_1 or later to mitigate the risk. Until patched, avoid using CurlAsyncHTTPClient with untrusted header data or sanitize header values to remove CRLF characters before sending requests.

Description

Tornado's CurlAsyncHTTPClient class allows injection of carriage return and line feed (CRLF) characters in HTTP request headers, enabling attackers to inject arbitrary headers or craft additional HTTP requests. This occurs because Tornado does not validate header values before passing them to libcurl, which does not filter control characters. Applications using Tornado to send HTTP requests with untrusted header data are vulnerable to this issue, which can facilitate server-side request forgery (SSRF) exploitation. A fix is available in Tornado version 2.2.0_1.

References

Community reviews

Loading reviews…