Loading vulnerability…
PowerJob versions 4.x through 5.1.2 contain an unauthenticated remote code execution vulnerability in the Server-Worker transport layer's /friend/process endpoint. The endpoint permits remote code execution without requiring authentication.
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 two-file repository contains a Python 3 operational exploit and supporting Markdown documentation for an unauthenticated remote-code-execution issue in PowerJob Server. The script targets the HTTP transport endpoint /friend/process on port 10010 and submits a RemoteProcessReq JSON object that names the Spring bean tech.powerjob.server.core.evaluator.GroovyEvaluator and its evaluate method. It supplies attacker-controlled Groovy which launches /bin/sh -c with an arbitrary command. Successful responses are parsed as JSON and the AskResponse data field is Base64-decoded to display command output. The optional --reverse-shell mode creates a background Bash /dev/tcp reverse shell, while -p/--proxy routes requests through an HTTP proxy. The reported vulnerability chain is missing authentication on PowerJob transport services, attacker-controlled class/method reflection, and direct Groovy ScriptEngine evaluation. No CVE identifier is supplied. The exploit is not a scanner or detection-only utility and contains no evident destructive/fake behavior, though it provides direct RCE and reverse-shell capability.
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.