Vault Vulnerable to Cache-Timing Attacks During Seal and Unseal Operations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.13.1, 1.12.5, 1.11.9, 1.11.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
HashiCorp Vault's implementation of Shamir's secret sharing used precomputed table lookups, and was vulnerable to cache-timing attacks. An attacker with access to, and the ability to observe a large number of unseal operations on the host through a side channel may reduce the search space of a brute force effort to recover the Shamir shares. Fixed in Vault 1.13.1, 1.12.5, and 1.11.9.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- HashiCorp Vault
From 1.13.0 · fixed in 1.13.1; From 1.12.0 · fixed in 1.12.5; From 1.11.0 · fixed in 1.11.9; fixed in 1.11.0
- HashiCorp Vault Enterprise
From 1.13.0 · fixed in 1.13.1; From 1.12.0 · fixed in 1.12.5; From 1.11.0 · fixed in 1.11.9; fixed in 1.11.0
- github.com/hashicorp/vaultGo
fixed in 1.11.9
- github.com/hashicorp/vaultGo
From 1.12.0 · fixed in 1.12.5
- github.com/hashicorp/vaultGo
From 1.13.0 · fixed in 1.13.1
- github.com/hashicorp/vaultGo
fixed in 1.11.9; From 1.12.0 · fixed in 1.12.5; From 1.13.0 · fixed in 1.13.1