Loading vulnerability…
Rambox 0.6.9 is vulnerable to a stored cross-site scripting (XSS) attack in the service name field when adding or editing a service. The application fails to properly sanitize user-supplied input in this field, allowing an attacker to inject malicious JavaScript code. In the context of an Electron application, this XSS can be leveraged to execute arbitrary OS commands via Node.js APIs, for example by using a crafted payload in the onerror attribute of an IMG element.
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 contains an exploit for CVE-2019-17625, a stored XSS vulnerability in Rambox 0.6.9. The main exploit script, 'nyquil.py', is a Python tool that modifies the local LevelDB database used by Rambox to inject a malicious payload into the configuration of a Discord service. The payload is a JavaScript XSS vector that, when rendered by Rambox (which runs on NodeJS), executes a reverse shell command using Node's 'child_process' module. The reverse shell connects back to an attacker-specified IP and port using netcat and bash, leveraging a named pipe at '/tmp/f'. The exploit requires local access to the victim's files and is primarily tested on macOS. The repository also includes a requirements.txt for dependencies and a README.md with usage instructions and a PoC GIF. No network endpoints are hardcoded; the attacker supplies the IP and port at runtime. The exploit is operational and demonstrates a practical attack chain from local file modification to remote code execution via stored XSS in an Electron-based application.
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.