CVE-2013-0282
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenStack Keystone Grizzly before 2013.1, Folsom 2012.1.3 and earlier, and Essex does not properly check if the (1) user, (2) tenant, or (3) domain is enabled when using EC2-style authentication, which allows context-dependent attackers to bypass access restrictions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenStack Keystone's EC2-style authentication mechanism fails to validate whether the user, tenant, or domain is in an enabled state before allowing access. This allows authenticated attackers with valid EC2 credentials to bypass access restrictions and potentially access resources even after their account, tenant, or domain has been disabled.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2012.1, <= 2012.1.3>= 2012.2, <= 2012.2.4= 2013.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Keystone versionRun 'keystone --version' or check the package manager (dpkg -l | grep keystone, rpm -qa | grep keystone) to find the installed Keystone versionAffected if Version is 2012.1.3 or earlier in the 2012.1 branch, 2012.2.4 or earlier in the 2012.2 branch, or exactly 2013.1
-
Confirm EC2 credential usageReview your Keystone configuration file (typically keystone.conf) for any ec2_* settings, or check if any users have ec2 credentials (access keys) issuedAffected if EC2-style credentials exist in the system
-
Check EC2 authentication endpointList Keystone endpoints and verify that EC2-style authentication service endpoint exists (typically /v2.0/ec2tokens)Affected if EC2 authentication endpoint is registered and accessible
-
Inspect token validation settingsExamine Keystone configuration for token validation settings, specifically looking at whether the 'enabled' flag is being checked during EC2-style authenticationAffected if EC2 credentials can be validated without checking user/tenant/domain enabled status
Your environment is affected if you run a vulnerable Keystone version AND have EC2-style authentication enabled, because disabled accounts can still authenticate via EC2 credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Keystone to Grizzly 2013.1 or later, Folsom 2012.1.4 or later, or apply the vendor patch for Essex versions. Alternatively, disable EC2-style authentication if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-0282 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data