Vault's Transit Secrets Engine Allowed Nonce Specified without Convergent Encryption
- 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.14.3, 1.13.7, 1.12.11, 1.12.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: total
Summary
HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption disabled. The encrypt endpoint, in combination with an offline attack, could be used to decrypt arbitrary ciphertext and potentially derive the authentication subkey when using transit secrets engine without convergent encryption. Introduced in 1.6.0 and fixed in 1.14.3, 1.13.7, and 1.12.11.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- HashiCorp Vault
From 1.14.0 · fixed in 1.14.3; From 1.13.0 · fixed in 1.13.7; From 1.12.0 · fixed in 1.12.11; From 1.6.0 · fixed in 1.12.0
- HashiCorp Vault Enterprise
From 1.14.0 · fixed in 1.14.3; From 1.13.0 · fixed in 1.13.7; From 1.12.0 · fixed in 1.12.11; From 1.6.0 · fixed in 1.12.0
- github.com/hashicorp/vaultGo
From 1.6.0 · fixed in 1.12.11
- github.com/hashicorp/vaultGo
From 1.13.0 · fixed in 1.13.7
- github.com/hashicorp/vaultGo
From 1.14.0 · fixed in 1.14.3
- github.com/hashicorp/vaultGo
From 1.6.0 · fixed in 1.12.11; From 1.13.0 · fixed in 1.13.7; From 1.14.0 · fixed in 1.14.3