# CVE-2013-2157: Auth bypass in n/a

> Remote attackers can bypass authentication in OpenStack Keystone when LDAP anonymous binding is enabled, gaining unauthorized access.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2157, GHSA-w396-2gg4-mxgv, RHSA-2013:0994, RHSA-2013:1083

## What is CVE-2013-2157?

CVE-2013-2157 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Aug 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenStack Keystone Folsom, Grizzly before 2013.1.3, and Havana, when using LDAP with Anonymous binding, allows remote attackers to bypass authentication via an empty password.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-2157?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openstack-keystone` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.4-3.el6ost |
| `openstack-keystone-doc` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.4-3.el6ost |
| `python-keystone` | Red Hat:openstack:2::el6 | All versions | 0:2012.2.4-3.el6ost |
| `openstack-keystone` | Red Hat:openstack:3::el6 | All versions | 0:2013.1.2-2.el6ost |
| `openstack-keystone-doc` | Red Hat:openstack:3::el6 | All versions | 0:2013.1.2-2.el6ost |
| `python-keystone` | Red Hat:openstack:3::el6 | All versions | 0:2013.1.2-2.el6ost |

Products: Openstack Keystone.

## How do I fix CVE-2013-2157?

Upgrade to a fixed version.

## Is CVE-2013-2157 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12690](https://insights.sbomify.com/CVE-2020-12690/): Insufficient Session Expiration in OpenStack Keystone (high 8.8)
- [CVE-2019-19687](https://insights.sbomify.com/CVE-2019-19687/): OpenStack Keystone Credential Leakage (high 8.8)
- [CVE-2026-43001](https://insights.sbomify.com/CVE-2026-43001/): OpenStack Keystone has an Incorrect Authorization Issue (high 7.9)
- [CVE-2014-2828](https://insights.sbomify.com/CVE-2014-2828/): OpenStack Identity (Keystone) DoS through V3 API authentication chaining (high 7.8)
- [CVE-2021-38155](https://insights.sbomify.com/CVE-2021-38155/): OpenStack Keystone allows information disclosure during account locking (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2157 and fix it if it is affected.

What it is: CVE-2013-2157 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Aug 2013. 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-2013-2157 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2013-2157/ (Markdown: https://insights.sbomify.com/CVE-2013-2157/index.md)
```

## Sources

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

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