CVE-2024-0195 is a critical code injection vulnerability in spider-flow version 0.4.3, specifically in the FunctionService.saveFunction method within src/main/java/org/spiderflow/controller/FunctionController.java. The vulnerability allows remote attackers to inject and execute arbitrary code via crafted input to the affected function. The exploit has been publicly disclosed and is available for use.
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 a Nuclei template (CVE-2024-0195.yaml) and a detailed README for exploiting CVE-2024-0195, a critical remote code execution vulnerability in spider-flow 0.4.3. The main exploit is a Nuclei YAML file that sends a crafted POST request to the /function/save endpoint, injecting Java code that executes arbitrary system commands on the server. The exploit uses out-of-band DNS callbacks (e.g., interactsh-url or dnslog.cn) to verify successful code execution. The README provides background, impact, mitigation advice, and a proof-of-concept HTTP request. The repository is structured for use with the Nuclei scanning framework and is a working proof-of-concept for unauthenticated RCE against vulnerable spider-flow instances.
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.