Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2014-0074: Apache Shiro LDAP Empty-Credential Authentication Bypass

Published Oct 6, 2014 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS5.5%93rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2014-0074CWE-287 · Improper Authentication

CVE-2014-0074 is an improper-authentication vulnerability in Apache Shiro 1.x before 1.2.3 when Shiro uses an LDAP backend configured to permit unauthenticated binds. Shiro can treat an LDAP bind made with an empty username or an empty password as successful authentication, allowing authentication without valid user credentials.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker may bypass application authentication and obtain access as an authenticated user without supplying a valid username or password. The resulting authorization level depends on the application's post-authentication authorization configuration and LDAP realm behavior.

Mitigation

If you can’t patch tonight, do this now.

Configure the LDAP server to disallow unauthenticated or anonymous bind operations. Enforce application-side validation that rejects empty usernames and passwords before LDAP authentication is attempted.

Remediation

Patch, then assume compromise.

Upgrade Apache Shiro to version 1.2.3 or later. For affected Red Hat JBoss Fuse 6.1.0 and Red Hat JBoss A-MQ 6.1.0 deployments, apply the applicable Rollup Patch 1 security update.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationShiroapplication
FAQ

Frequently asked questions

Is CVE-2014-0074 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2014-0074 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2014-0074?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2014-0074.
Is there a patch for CVE-2014-0074?
Upgrade Apache Shiro to version 1.2.3 or later. For affected Red Hat JBoss Fuse 6.1.0 and Red Hat JBoss A-MQ 6.1.0 deployments, apply the applicable Rollup Patch 1 security update.
What products are affected by CVE-2014-0074?
Apache Software Foundation Shiro.
How severe is CVE-2014-0074?
CVE-2014-0074 has a CVSS v2 score of 7.5 (High) and an EPSS score of 5.5% (93rd percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.