Ubuntu LinuxOperating system · Canonical
CVE-2020-12692
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 · uneditedAn issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.
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 API lacks a time-to-live (TTL) validation for AWS Signature V4 authorization headers. An attacker who intercepts a valid Authorization header can replay it indefinitely to obtain new OpenStack tokens, as there is no expiration check on the signature.
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
Ubuntu LinuxOperating system
= 18.04< 15.0.1= 16.0.0CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 OpenStack Keystone installationRun 'keystone --version' or check package manager (dpkg -l | grep keystone, rpm -qa | grep keystone) to find if Keystone is installedAffected if Keystone is not installed or the command fails - the service is not present in the environment
-
Determine installed Keystone versionExecute 'keystone --version' or check the package version via your package manager (dpkg -l python-keystone or rpm -qa python3-keystone)Affected if Version is less than 15.0.1 or equals exactly 16.0.0 (vulnerable versions)
-
Confirm EC2 API is enabledCheck Keystone configuration files (typically /etc/keystone/keystone.conf or /etc/keystone.conf) for the [ec2] section, or list enabled WSGI modules/services that handle EC2 requestsAffected if The EC2 API endpoint extension is enabled and accessible in the environment
If Keystone is installed, the version is 15.0.1 or higher (or 16.0.1+), and the EC2 API is not enabled, the environment is not vulnerable to CVE-2020-12692.
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 data15.0.1
Upgrade Keystone to version 15.0.1 or 16.0.0 or later, which include the signature TTL check. Alternatively, implement network-level controls to prevent authorization header interception.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12692 — 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-2020-12692 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