Loading vulnerability…
CVE-2020-6514 is a heap corruption vulnerability in the WebRTC component of Google Chrome prior to version 84.0.4147.89. The flaw arises from inappropriate implementation in the handling of SCTP streams, which could allow an attacker in a privileged network position to craft malicious SCTP traffic that corrupts heap memory.
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 contains a proof-of-concept exploit for CVE-2020-6514, targeting the WebRTC implementation in several popular Android applications (Signal, Duo, JioChat, VK, OK). The exploit leverages Frida to dynamically hook and manipulate native functions in the WebRTC stack of the target application, allowing the attacker to alter and inspect SCTP packets during a WebRTC call. The repository is organized by target application, with each directory containing a JavaScript file (Frida script) that performs the hooking and a Python script that loads the Frida script into the target app's process. There is also a helper script (fixsdp.py) for manipulating SDP in VK/OK. The README provides technical background and usage notes, including the need for specific binary offsets and the limitations of the exploit. The exploit is a POC and requires the attacker to have local access to their own device with the vulnerable app installed and the ability to initiate a call to the victim. The main attack vector is network-based, exploiting the WebRTC protocol during peer-to-peer calls. No hardcoded IPs or URLs are present; the main fingerprintable endpoints are Android package names and native library files.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.