Loading vulnerability…
Socket.IO contains an unhandled error-event vulnerability in which a specially crafted Socket.IO packet can cause an error event that is not caught by the server. The resulting uncaught exception terminates the Node.js process. The issue affects Socket.IO 3.x and 4.x versions before 4.6.2 and Socket.IO 2.x versions before 2.5.1.
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.
Repository is a Dockerized proof-of-concept for CVE-2024-38355 (Socket.IO crash/DoS). It contains two Node.js components: (1) a vulnerable Socket.IO server (server/index.js) pinned to socket.io@4.6.1 that registers a 'process_data' handler which can throw an uncaught exception when receiving {trigger:'crash'} and does not attach a per-socket 'error' listener; (2) an exploit client (exploit/exploit.js) using socket.io-client@4.6.1 that first performs a normal request to demonstrate service health, then reconnects and emits the malicious 'process_data' payload to crash the server, and finally attempts a reconnect to verify the service is unreachable. Orchestration is via docker-compose.yml exposing port 3000 and passing TARGET_URL=http://vulnerable-server:3000 to the exploit container. No persistence, RCE, or data exfiltration is present—capability is limited to remote denial-of-service by process crash.
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.