Apache Tomcat contains an observable-discrepancy flaw in FORM authentication handling. In affected releases, improper error checking in the MemoryRealm, and in affected earlier versions of DataSourceRealm and JDBCRealm, produces distinguishable behavior when a malformed URL-encoded password is submitted during authentication. An unauthenticated remote attacker can use this behavior to determine whether a supplied username is valid.
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 2 candidates 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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Username enumeration through insufficient authentication error handling.
Username-enumeration information disclosure in FORM authentication realms.
An Apache Tomcat information-disclosure vulnerability that permits remote username enumeration when FORM authentication is enabled. Malformed URL encoding in the j_password parameter triggers improper error handling in the MemoryRealm, DataSourceRealm, and JDBCRealm authentication realms.
Authentication error-handling flaw allowing username enumeration.
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.