Loading vulnerability…
Apache Shiro versions prior to 1.7.1, when used in conjunction with Spring, contain an authentication bypass condition where a specially crafted HTTP request can cause Shiro to incorrectly treat a request as authenticated/authorized, allowing access to resources that should be protected by Shiro’s authentication checks.
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 is a proof-of-concept (POC) environment for demonstrating and analyzing CVE-2020-17523, an authentication bypass vulnerability in Apache Shiro when used with Spring. The project is a Java Spring Boot application configured with Apache Shiro 1.7.0, and includes a custom realm, Shiro configuration, and a login controller exposing /doLogin and /admin/* endpoints. The README provides a detailed analysis of the vulnerability, including two main bypass techniques: using encoded spaces (e.g., /admin/%20) and encoded dots (e.g., /admin/%2e) in the URL to bypass Shiro's authentication checks. The exploit works due to improper path normalization and tokenization in Shiro's path matching logic. The repository includes all necessary files to build and run the vulnerable environment, making it suitable for testing and understanding the exploit. No weaponized payloads are included; the focus is on demonstrating the authentication bypass via crafted HTTP requests.
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.