Loading vulnerability…
PowerJob Server 5.1.2, and likely earlier versions, uses a predictable signing key for HS256 JSON Web Token authentication. An attacker who derives or knows the key can forge authentication tokens accepted by the server, potentially obtaining authorization sufficient to invoke functionality that enables arbitrary code execution.
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 proof-of-concept and supporting README for an authentication-bypass vulnerability in PowerJob Server 5.1.2. PowerJob_jwt_key.py derives the HS256 signing key by concatenating the embedded BASE_SECURITY constant with MD5(JDBC URL), Base64-decoding the result, and signing a JWT locally with Python standard-library cryptographic functions. It computes the PWJB encryptedToken using the default password, forges a seven-day PWJB_ADMIN token, then uses requests to POST to /namespace/list with the PowerJwt header and report whether authentication succeeded. No shell, persistence, file modification, or remote-code-execution payload is present. The README describes the underlying predictable-key condition, default-deployment assumptions, web-console administrator impact, and a claimed related OpenAPI token-forgery path not directly exercised by the script.
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.
6 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.