Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

OpenStack Keystone EC2 API AWS Signature V4 Replay Due to Missing TTL Check

IdentifiersCVE-2020-12692CWE-294· Authentication Bypass by…

CVE-2020-12692 affects OpenStack Keystone before 15.0.1 and 16.0.0. The vulnerability is in Keystone's EC2 credential authentication handling for the EC2 API, where AWS Signature Version 4 requests are accepted without enforcing a signature time-to-live (TTL) check. Because the Authorization header can be replayed after capture, a previously valid signed request can be reused to obtain a new OpenStack token repeatedly. The issue is specifically described as allowing an attacker who can sniff the Authorization header to reissue an OpenStack token an unlimited number of times.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthorized reuse of captured AWS Signature V4 authentication material against Keystone's EC2 API. An attacker can replay a sniffed Authorization header to repeatedly obtain OpenStack tokens associated with the victim, resulting in unauthorized access and persistent token reissuance without needing the victim's secret material beyond the captured header. This can enable continued impersonation of the affected identity and access to resources permitted to that account.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of the Keystone EC2 API to untrusted networks, enforce transport security to reduce the chance of Authorization header capture, and monitor for anomalous or repeated token issuance via the EC2 authentication path. Limiting access to the affected endpoint and rotating exposed credentials may reduce risk, but the definitive fix is upgrading to a patched Keystone release.

Remediation

Patch, then assume compromise.

Upgrade OpenStack Keystone to a fixed release. The provided advisory indicates affected versions are Keystone before 15.0.1 and 16.0.0, and remediation is to update to 15.0.1 or later in the 15.x series, or to 16.0.0 or later, as applicable in the deployment.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CanonicalUbuntu Linuxapplication
OpenstackKeystoneapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.