CVE-2022-40186GO-2022-1021BIT-VAULT-2022-40186GHSA-7CGV-V83V-RR87
An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3.
- 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.9.9, 1.10.6, 1.11.3
- 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
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
An issue was discovered in HashiCorp Vault and Vault Enterprise before 1.11.3. A vulnerability in the Identity Engine was found where, in a deployment where an entity has multiple mount accessors with shared alias names, Vault may overwrite metadata to the wrong alias due to an issue with checking the proper alias assigned to an entity. This may allow for unintended access to key/value paths using that metadata in Vault.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- github.com/hashicorp/vaultGo
From 1.8.0 · fixed in 1.9.9; From 1.10.0 · fixed in 1.10.6; From 1.11.0 · fixed in 1.11.3
- github.com/hashicorp/vaultGo
From 1.11.0 · fixed in 1.11.3
- github.com/hashicorp/vaultGo
From 1.10.0 · fixed in 1.10.6
- github.com/hashicorp/vaultGo
From 1.8.0 · fixed in 1.9.9