CVE-2013-2157: OpenStack Keystone Folsom, Grizzly before 2013.1.3, and Havana, when using LDAP with Anonymous binding, allows remote attackers to bypass…
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.1% (FIRST EPSS); higher than 88% of all records.
- Fixed version: keystone (Debian:12) 2013.1.2-1; openstack-keystone (Red Hat:openstack:2::el6) 0:2012.2.4-3.el6ost; openstack-keystone-doc (Red Hat:openstack:2::el6) 0:2012.2.4-3.el6ost.
Low priority for now. Upgrade to keystone (Debian:12) 2013.1.2-1; openstack-keystone (Red Hat:openstack:2::el6) 0:2012.2.4-3.el6ost; openstack-keystone-doc (Red Hat:openstack:2::el6) 0:2012.2.4-3.el6ost or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 20, 2013
- Updated
- Jun 16, 2026
- EPSS
- 3.1% · 88th percentile
- CWE
- CWE-287
Report tools
Action score
18
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openstack | keystone | cpe:2.3:a:openstack:keystone |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- openstack keystone2012.2 and later · up to 2012.2.4 inclusive
- openstack keystone2013.1 and later · before 2013.1.3
- openstack keystone2013.2 and later · up to 2013.2.4 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | keystone | before 2013.1.2-1 | 2013.1.2-1 |
| Red Hat:openstack:2::el6 | openstack-keystone | before 0:2012.2.4-3.el6ost | 0:2012.2.4-3.el6ost |
| Red Hat:openstack:2::el6 | openstack-keystone-doc | before 0:2012.2.4-3.el6ost | 0:2012.2.4-3.el6ost |
| Red Hat:openstack:2::el6 | python-keystone | before 0:2012.2.4-3.el6ost | 0:2012.2.4-3.el6ost |
| Red Hat:openstack:3::el6 | openstack-keystone | before 0:2013.1.2-2.el6ost | 0:2013.1.2-2.el6ost |
| Red Hat:openstack:3::el6 | openstack-keystone-doc | before 0:2013.1.2-2.el6ost | 0:2013.1.2-2.el6ost |
| Red Hat:openstack:3::el6 | python-keystone | before 0:2013.1.2-2.el6ost | 0:2013.1.2-2.el6ost |
Same product
openstack: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-12691An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.36Monitor
- CVE-2020-12690An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0.36Monitor
- CVE-2019-19687OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2013-2006May 21, 2013 · OpenStack Identity (Keystone) Grizzly 2013.1.1, when DEBUG mode logging is enabled, logs the (1) admin_token and (2) LDAP password in…8Monitor
- ← EarlierCVE-2013-2059May 21, 2013 · OpenStack Identity (Keystone) Folsom 2012.2.4 and earlier, Grizzly before 2013.1.1, and Havana does not immediately revoke the…25Monitor
- Later →CVE-2013-4294Sep 23, 2013 · The (1) mamcache and (2) KVS token backends in OpenStack Identity (Keystone) Folsom 2012.2.x and Grizzly before 2013.1.4 do not properly…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:keystone | 2013.1.2-1 · Debian:12 | Package registry (OSV) |
| red hat:openstack-keystone | 0:2013.1.2-2.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:openstack-keystone-doc | 0:2013.1.2-2.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:python-keystone | 0:2013.1.2-2.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- M
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:M/Au:N/C:N/I:P/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.