Loading vulnerability…
A vulnerability in the ejs (Embedded JavaScript templates) package for Node.js, prior to version 3.1.10, allows for prototype pollution due to insufficient protection against object property pollution. This can occur when user-supplied input is not properly sanitized before being used in template rendering, potentially allowing attackers to manipulate object prototypes.
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 (PoC) exploit for CVE-2024-33883, a remote code execution (RCE) vulnerability in ejs@3.1.9 (and all versions below 3.1.10) due to insufficient validation against prototype pollution. The repository contains a Node.js Express application (app.js) that exposes three HTTP endpoints: '/', '/pollute', and '/check'. The '/pollute' endpoint allows an attacker to set arbitrary properties on Object.prototype, enabling prototype pollution. By manipulating the 'client' and 'escapeFunction' properties, an attacker can inject and execute arbitrary JavaScript code during template rendering, leading to RCE. The exploit demonstrates writing a webshell (payload.js) to disk and executing arbitrary system commands, leaking their output via error messages. The Dockerfile provides an environment for running the PoC. The repository structure is straightforward, with the main logic in app.js, the payload in payload.js, and supporting files for package management and demonstration. The exploit targets Node.js applications using vulnerable versions of ejs and requires the attacker to have access to endpoints that allow prototype pollution and template rendering.
1 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.