A policy bypass vulnerability existed in the Content Security Policy (CSP) implementation in Google Chrome prior to version 84.0.4147.89. A remote attacker could craft a malicious HTML page that would bypass the intended CSP restrictions, potentially allowing the execution of unauthorized scripts or loading of restricted resources.
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 (1 hidden).
This repository provides a proof-of-concept (POC) exploit for CVE-2020-6519, a vulnerability in Chromium-based browsers (Chrome, Opera, Edge) that allows a full bypass of Content Security Policy (CSP) restrictions. The main exploit is implemented in 'CVE-2020-6519-TEST-IT-YOURSELF.js', which uses JavaScript to inject an iframe with a 'javascript:' URL, enabling the loading of external scripts, objects, and iframes from a forbidden domain (malicious.com) despite restrictive CSP rules. The POC directory contains HTML files with different CSP configurations and JavaScript files that demonstrate both failed and successful bypass attempts. The exploit can be used to steal cookies or execute arbitrary scripts from a remote attacker-controlled domain. The repository is structured with clear separation between demonstration files, exploit code, and documentation, making it easy to reproduce and understand the vulnerability's impact.
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.