Loading vulnerability…
In Apache Shiro before 1.1.0 and JSecurity 0.9.x, the software fails to canonicalize URI paths before comparing them to access control entries in the shiro.ini configuration file. This allows attackers to craft requests with non-canonical paths (such as /./account/index.jsp) to bypass intended access restrictions, as the path comparison does not account for alternate representations of the same resource.
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 (2 hidden).
This repository contains a Nuclei proof-of-concept (POC) YAML template for exploiting CVE-2010-3863, a path traversal vulnerability in Apache Shiro. The main file, 'poc.yml', defines an HTTP GET request to the '/./admin/' path, attempting to bypass access controls via path traversal. The exploit checks for a 200 OK response and the presence of 'rootAccount Info' in the response body, indicating successful unauthorized access to admin information. The repository also includes a brief README in Chinese describing the vulnerability and steps for local testing, and a .gitattributes file for text normalization. No hardcoded IP addresses or external domains are present; the only fingerprintable endpoint is the '/./admin/' HTTP path. The exploit is a POC and does not include weaponized or customizable payloads.
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.