The server component of SerNet verinice before version 1.22.2 is vulnerable to insecure Java deserialization. Remote authenticated attackers can exploit this flaw to execute arbitrary code on the server by sending specially crafted serialized objects.
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 provides a Python 2 proof-of-concept exploit for CVE-2021-36981, targeting Verinice.Pro 1.22.1's unsafe Java deserialization vulnerability. The main file, 'send-verinice-deserial.py', allows an authenticated attacker to execute arbitrary commands on the target server by sending a malicious serialized Java object (generated with ysoserial) to the vulnerable HTTP endpoint '/veriniceserver/service/commandServiceHttpInvoker'. The script supports both single-gadget and brute-force modes, leveraging multiple ysoserial gadgets, and can trigger various payloads including command execution, file writes, SSRF, and reverse shells. The exploit requires a valid session cookie (JSESSIONID) and access to the ysoserial JAR. The script also includes hardcoded endpoints for attacker infrastructure (reverse shell IP/port, Burp Collaborator) and uses a local proxy for traffic interception. The repository consists of a README and the exploit script, with the latter being the main entry point and containing all exploit logic.
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.