Skip to content
Fencer Intel
high 7.5

CVE-2014-0074 json

Apache Shiro 1.x before 1.2.3, when using an LDAP server with unauthenticated bind enabled, allows remote attackers to bypass authenticatio…

published 2014-10-06 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0167

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.5%
EPSS 5.5% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

Apache Shiro 1.x before 1.2.3, when using an LDAP server with unauthenticated bind enabled, allows remote attackers to bypass authentication via an empty (1) username or (2) password.

Patch / fix

  • shiro Debian 14, Debian 13, Debian 12 1.2.3-1

debian advisories DEBIAN-CVE-2014-0074

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0074 updated cvss 7.5

Shiro: successful authentication without specifying user name or password

  • Red Hat JBoss Fuse Service Works 6 shiro shiro
    affected: no fix planned “Will not fix”
  • Red Hat Fuse ESB Enterprise 7.1.0 Red Hat Fuse Management Console 7.1.0 Red Hat Fuse MQ Enterprise 7.1.0
    fixed: vendor fix RHSA-2014:1369
  • Red Hat JBoss A-MQ 6.1 Red Hat JBoss Fuse 6.1
    fixed: vendor fix RHSA-2014:1351

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.49% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • issues.apache.org https://issues.apache.org/jira/browse/SHIRO-460 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.