Loading vulnerability…
In Apache Shiro before version 1.9.1, the RegexRequestMatcher component can be misconfigured such that, when using RegExPatternMatcher with a . in the regular expression, it may be bypassed on certain servlet containers. This can result in improper authorization checks, allowing unauthorized access to protected resources.
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.
. inappropriately). Restrict access to sensitive endpoints through additional security controls at the web server or application level until the patch can be applied.Patch, then assume compromise.
. character.1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository is a minimal proof-of-concept (POC) environment for demonstrating CVE-2022-32532, an authentication bypass vulnerability in Apache Shiro versions prior to 1.9.1. The vulnerability arises from improper handling of regular expressions in the RegExPatternMatcher, allowing attackers to bypass authentication by inserting newline (%0a) or carriage return (%0d) characters in the URL path. The repository is structured as a Spring Boot web application using shiro-spring 1.6.0, with custom filter and filter factory classes to demonstrate the vulnerable and patched behaviors. The main entry point is ShiroCve202232532Application.java, and the vulnerable endpoint is /permit/{value}. The README provides detailed reproduction steps and mitigation guidance. No weaponized payload is included; the POC demonstrates the 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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.