Loading vulnerability…
Apache Shiro 1.x and 2.x releases prior to 2.0.7 contain an observable timing discrepancy in authentication handling. Processing paths for a non-existent username and for an existing username supplied with an incorrect password differ sufficiently that repeated timing measurements may distinguish the two failure conditions. This can enable username enumeration.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A low-severity observable timing discrepancy in Apache Shiro permits potential username enumeration by distinguishing authentication failures for nonexistent users from incorrect passwords. The content identifies Apache Shiro 1.x and 2.x before 2.0.7 as affected and describes a local attack as the most likely vector. CVSS v3 base score: 2.5.
Timing side-channel in Apache Shiro that can enable username enumeration by distinguishing responses for existing vs non-existing users.
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.