Inversoft Prime-JWT versions before commit abb0d479389a2509f939452a6767dc424bb5e6ba contain an input-validation flaw in JWTDecoder.decode. A crafted JWT using the unsigned "none" algorithm in an otherwise valid header can cause incorrect JWT signature validation.
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 (1 hidden).
This repository contains a single Python script, 'jwtbruteforcer.py', which serves as a proof-of-concept tool for testing JWT implementations for the CVE-2018-1000531 vulnerability and for brute-forcing JWT secret keys. The tool first checks if a given JWT token is vulnerable to the 'alg':'none' attack (CVE-2018-1000531) by manipulating the token header and attempting to decode it without signature verification. If the target is not vulnerable, the tool proceeds to brute-force the JWT secret key using a user-supplied wordlist file. The script is interactive, requiring the user to input a JWT token and the path to a wordlist file. The repository is structured simply, with a license, a brief README, and the main exploit script. No network endpoints or hardcoded targets are present; the tool operates locally on user-supplied data.
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.