Skip to content

HashiCorp Vault vulnerable to incorrect metadata access

Critical severity GitHub Reviewed Published Sep 23, 2022 to the GitHub Advisory Database • Updated Feb 3, 2023

Package

gomod github.com/hashicorp/vault (Go)

Affected versions

>= 1.11.0, < 1.11.3
>= 1.10.0, < 1.10.6
>= 1.8.0, < 1.9.9

Patched versions

1.11.3
1.10.6
1.9.9

Description

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.

References

Published by the National Vulnerability Database Sep 22, 2022
Published to the GitHub Advisory Database Sep 23, 2022
Reviewed Sep 23, 2022
Last updated Feb 3, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.138%
(51st percentile)

Weaknesses

No CWEs

CVE ID

CVE-2022-40186

GHSA ID

GHSA-7cgv-v83v-rr87

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.