Loading vulnerability…
CVE-2020-28502 affects the npm packages xmlhttprequest (versions before 1.7.0) and all versions of xmlhttprequest-ssl. When requests are made synchronously (i.e., async=false in xhr.open), attacker-controlled input that flows into xhr.send can lead to arbitrary code being injected and executed within the context of the Node.js process using the library.
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.
xhr.send in synchronous request mode, potentially enabling full compromise of the running application process (e.g., execution of attacker-supplied code with the application’s privileges).If you can’t patch tonight, do this now.
xhr.send, especially when using synchronous requests (async=false). Prefer asynchronous requests and validate/sanitize any data provided to xhr.send.Patch, then assume compromise.
xmlhttprequest to >= 1.7.0. Upgrade xmlhttprequest-ssl to >= 1.6.2.1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a Proof-of-Concept (PoC) exploit for CVE-2020-28502, a remote code execution vulnerability in the 'xmlhttprequest' npm package (before 1.7.0) and all versions of 'xmlhttprequest-ssl'. The repository contains a simple Node.js Express application (app.js) that exposes a web interface (html/index.html) on port 3000, allowing users to submit a URL and POST body. The server uses the vulnerable 'xmlhttprequest' package to send a synchronous POST request to the user-supplied URL with the user-supplied body. Due to improper handling of user input in the vulnerable package, an attacker can inject arbitrary JavaScript code into the 'xhr.send' call, leading to remote code execution on the server. The README provides example payloads for writing a file and spawning a reverse shell. The Dockerfile allows for easy setup and testing of the exploit. The main entry point is app.js, and the exploit is demonstrated via the web interface at http://localhost:3000. The repository is structured as a PoC and is not weaponized or part of a larger framework.
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.