# CVE-2014-0097: Improper Authentication in Spring Security

> Attackers can bypass authentication with empty passwords if the LDAP directory allows anonymous binds, affecting Spring Security users.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-gv9v-c375-hvmg

## What is CVE-2014-0097?

CVE-2014-0097 is a high-severity authentication bypass vulnerability in Pivotal Spring Security, published on 25 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2014-0097?

4 open source packages ship an affected version, including org.springframework.security:spring-security-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.security:spring-security-core` | Maven | From 3.1.0 | 3.1.5.RELEASE |
| `org.springframework.security:spring-security-core` | Maven | From 3.1.0 | 3.1.5.RELEASE |
| `org.springframework.security:spring-security-core` | Maven | From 3.2.0 | 3.2.2.RELEASE |
| `org.springframework.security:spring-security-core` | Maven | From 3.2.0 | 3.2.2.RELEASE |

Products: Vmware Spring Security.

## How do I fix CVE-2014-0097?

Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 3.1.5.RELEASE or 3.2.2.RELEASE.

## Is CVE-2014-0097 being exploited?

There is no known exploitation of CVE-2014-0097 in the wild and no public exploit code.

## Other vulnerabilities in Pivotal Spring Security

- [CVE-2014-3527](https://insights.sbomify.com/CVE-2014-3527/): Authorization Bypass in Spring Security (critical 9.8)
- [CVE-2026-59354](https://insights.sbomify.com/CVE-2026-59354/): Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata (critical 9.6)
- [CVE-2026-59270](https://insights.sbomify.com/CVE-2026-59270/): Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces (critical 9.4)
- [CVE-2026-22732](https://insights.sbomify.com/CVE-2026-22732/): Under Some Conditions Spring Security HTTP Headers Are not Written (critical 9.1)
- [CVE-2023-34034](https://insights.sbomify.com/CVE-2023-34034/): Access Control Bypass in Spring Security (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0097 and fix it if it is affected.

What it is: CVE-2014-0097 is a high-severity authentication bypass vulnerability in Pivotal Spring Security, published on 25 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0097 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.security:spring-security-core (Maven): affected from 3.1.0; fixed in 3.1.5.RELEASE
- org.springframework.security:spring-security-core (Maven): affected from 3.1.0; fixed in 3.1.5.RELEASE
- org.springframework.security:spring-security-core (Maven): affected from 3.2.0; fixed in 3.2.2.RELEASE
- org.springframework.security:spring-security-core (Maven): affected from 3.2.0; fixed in 3.2.2.RELEASE

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-0097/ (Markdown: https://insights.sbomify.com/CVE-2014-0097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-0097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-0097
- OSV: https://osv.dev/vulnerability/CVE-2014-0097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-0097/
Summaries are generated and may contain mistakes; the official description above is the record.