LiveActive security incident?Get immediate response
CVE Record

CVE-2014-0097: The ActiveDirectoryLdapAuthenticator in Spring Security 3.2.0 to 3.2.1 and 3.1.0 to 3.1.5 does not check th...

The ActiveDirectoryLdapAuthenticator in Spring Security 3.2.0 to 3.2.1 and 3.1.0 to 3.1.5 does not check the password length. If the directory allows anonymous binds then it may incorrectly authenticate a user who supplies an empty password.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some older Spring Security versions could mistakenly log in a user who submits no password, but only when the application uses Active Directory LDAP authentication and the directory permits anonymous binds. This is a potentially serious authentication weakness, but the source bundle does not provide CVSS, exploit activity, or complete vendor remediation details.

Executive priority

Prioritize review for internet-facing or sensitive applications using legacy Spring Security with Active Directory login. Urgency rises if anonymous LDAP binds are enabled. No active exploitation evidence is provided in the source bundle.

Technical view

CVE-2014-0097 affects ActiveDirectoryLdapAuthenticator in Spring Security 3.1.0 through 3.1.5 and 3.2.0 through 3.2.1. The component did not check password length, so empty-password authentication could succeed when the backing directory allowed anonymous bind behavior.

Likely exposure

Exposure is likely limited to applications using the affected Spring Security versions with ActiveDirectoryLdapAuthenticator against an LDAP or Active Directory service that permits anonymous binds.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Practical risk depends on a specific configuration: vulnerable Spring Security, AD LDAP authentication, and directory anonymous-bind behavior.

Researcher notes

Key constraints are configuration-dependent. The CVE description names the affected component and version ranges, but the bundle lacks CVSS, CWE, proof of exploitation, and specific fixed release metadata. Treat Oracle references as downstream signals unless the relevant product advisory confirms impact.

Mitigation direction

  • Review Pivotal or successor vendor guidance for fixed Spring Security versions.
  • Upgrade Spring Security outside the affected version ranges.
  • Disable anonymous binds where business requirements allow.
  • Ensure application authentication rejects empty or missing passwords.
  • Check downstream vendor advisories, including Oracle CPU references, if bundled in products.

Validation and detection

  • Inventory applications for Spring Security 3.1.0-3.1.5 or 3.2.0-3.2.1.
  • Confirm whether ActiveDirectoryLdapAuthenticator is used.
  • Review LDAP or Active Directory anonymous-bind policy.
  • Verify authentication tests reject empty-password submissions.
  • Check logs for suspicious successful logins with missing password indicators.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-0097 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PivotalSpring Security3.2.0 to 3.2.1, 3.1.0 to 3.1.5Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.