Loading vulnerability…
A vulnerability in NodeBB, an open source Node.js-based forum software, allows attackers to exploit improper handling of plain objects with prototypes in socket.io message processing. By sending a specially crafted payload, an attacker can impersonate other users and take over their accounts. The vulnerability is due to prototype pollution, where attacker-controlled properties are injected into objects, leading to privilege escalation.
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 exploit for CVE-2022-46164, targeting NodeBB forum software. The main file, poc.py, is a Python script that exploits an authentication bypass vulnerability in NodeBB's socket.io implementation. The script allows an attacker to escalate privileges to admin for a specified user ID and retrieve API tokens from the server. It does so by establishing a socket.io session, performing a crafted handshake, and sending specific messages to escalate privileges and extract sensitive information. The script supports both HTTP and HTTPS, optional proxy configuration, and can use a provided express.sid cookie if two-factor authentication is enabled. The repository contains only one code file (poc.py), a README, a LICENSE, and a .gitignore. No hardcoded endpoints are present; the target domain is supplied via command-line arguments. The exploit is network-based and requires access to the NodeBB instance's socket.io endpoint.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.