Loading vulnerability…
CVE-2024-6197 is a vulnerability in libcurl’s ASN.1 parser, specifically in the utf8asn1str() function used to parse ASN.1 UTF-8 strings during certificate processing. When the function detects an invalid field and returns an error, it incorrectly calls free() on a 4-byte local stack buffer instead of heap-allocated memory. On hardened or modern malloc implementations, this typically causes an immediate abort and process crash. On allocators that accept the invalid pointer, the free operation can corrupt allocator state and lead to overwriting nearby stack memory with allocator-controlled metadata such as pointers and flags. The vulnerable code path can be reached when curl/libcurl processes a maliciously crafted TLS certificate presented by a server during connection establishment.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A curl vulnerability affecting CBL Mariner and Windows, included as advisory information in the October release.
A remote code execution vulnerability in open source Curl, exploitable when a client connects to a malicious server.
A remote code execution vulnerability in the open source Curl library.
A high-severity vulnerability in curl that could enable compromise when a user connects to a malicious/incorrect server (exact technical mechanism not specified in the content).
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.