Loading vulnerability…
CVE-2020-35669 is a CRLF injection vulnerability in the Dart http package up to version 0.12.2. If an attacker can control the HTTP method and the application uses the Request class directly, they can inject CRLF sequences into HTTP requests, potentially manipulating HTTP headers or request structure.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept exploit for CVE-2020-35669, targeting the Dart 'http' library (version 0.12.2). The exploit demonstrates how a crafted HTTP request can be constructed using Dart's Request class to inject or manipulate HTTP headers and paths, potentially leading to header injection or request smuggling vulnerabilities, especially in environments with reverse proxies. The main exploit logic is in 'main.dart', which sends a custom HTTP request to a target server. The README provides detailed instructions for setting up a dummy server (using netcat) to observe the crafted request and explains the security implications. The repository contains one main code file (main.dart), dependency files, and documentation. No framework is used; the exploit is a standalone Dart script. The endpoints involved include 'http://example.com/', 'http://localhost/llama', and the local IP '127.0.0.1:80' for testing. The exploit is a POC and does not include a weaponized or customizable payload.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.