Vulnerabilities (CVE)

Filtered by vendor Hashicorp Subscribe
Filtered by product Vault
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2023-3462 1 Hashicorp 1 Vault 2023-08-04 N/A 5.3 MEDIUM
HashiCorp's Vault and Vault Enterprise are vulnerable to user enumeration when using the LDAP auth method. An attacker may submit requests of existent and non-existent LDAP users and observe the response from Vault to check if the account is valid on the LDAP server. This vulnerability is fixed in Vault 1.14.1 and 1.13.5.
CVE-2021-27668 1 Hashicorp 1 Vault 2022-07-12 5.0 MEDIUM 5.3 MEDIUM
HashiCorp Vault Enterprise 0.9.2 through 1.6.2 allowed the read of license metadata from DR secondaries without authentication. Fixed in 1.6.3.
CVE-2022-30689 1 Hashicorp 1 Vault 2022-06-29 5.0 MEDIUM 5.3 MEDIUM
HashiCorp Vault and Vault Enterprise from 1.10.0 to 1.10.2 did not correctly configure and enforce MFA on login after server restarts. This affects the Login MFA feature introduced in Vault and Vault Enterprise 1.10.0 and does not affect the separate Enterprise MFA feature set. Fixed in 1.10.3.
CVE-2021-43998 1 Hashicorp 1 Vault 2022-01-07 5.5 MEDIUM 6.5 MEDIUM
HashiCorp Vault and Vault Enterprise 0.11.0 up to 1.7.5 and 1.8.4 templated ACL policies would always match the first-created entity alias if multiple entity aliases exist for a specified entity and mount combination, potentially resulting in incorrect policy enforcement. Fixed in Vault and Vault Enterprise 1.7.6, 1.8.5, and 1.9.0.
CVE-2021-45042 1 Hashicorp 1 Vault 2021-12-30 6.8 MEDIUM 4.9 MEDIUM
In HashiCorp Vault and Vault Enterprise before 1.7.7, 1.8.x before 1.8.6, and 1.9.x before 1.9.1, clusters using the Integrated Storage backend allowed an authenticated user (with write permissions to a kv secrets engine) to cause a panic and denial of service of the storage backend. The earliest affected version is 1.4.0.
CVE-2021-41802 1 Hashicorp 1 Vault 2021-10-19 5.5 MEDIUM 5.4 MEDIUM
HashiCorp Vault and Vault Enterprise through 1.7.4 and 1.8.3 allowed a user with write permission to an entity alias ID sharing a mount accessor with another user to acquire this other user’s policies by merging their identities. Fixed in Vault and Vault Enterprise 1.7.5 and 1.8.4.
CVE-2021-38553 1 Hashicorp 1 Vault 2021-09-07 2.1 LOW 4.4 MEDIUM
HashiCorp Vault and Vault Enterprise 1.4.0 through 1.7.3 initialized an underlying database file associated with the Integrated Storage feature with excessively broad filesystem permissions. Fixed in Vault and Vault Enterprise 1.8.0.
CVE-2020-25816 1 Hashicorp 1 Vault 2021-09-07 4.9 MEDIUM 6.8 MEDIUM
HashiCorp Vault and Vault Enterprise versions 1.0 and newer allowed leases created with a batch token to outlive their TTL because expiration time was not scheduled correctly. Fixed in 1.4.7 and 1.5.4.
CVE-2021-38554 1 Hashicorp 1 Vault 2021-08-25 3.5 LOW 5.3 MEDIUM
HashiCorp Vault and Vault Enterprise’s UI erroneously cached and exposed user-viewed secrets between sessions in a single shared browser. Fixed in 1.8.0 and pending 1.7.4 / 1.6.6 releases.
CVE-2020-35453 1 Hashicorp 1 Vault 2021-07-21 5.0 MEDIUM 5.3 MEDIUM
HashiCorp Vault Enterprise’s Sentinel EGP policy feature incorrectly allowed requests to be processed in parent and sibling namespaces. Fixed in 1.5.6 and 1.6.1.
CVE-2020-35177 1 Hashicorp 1 Vault 2021-07-21 5.0 MEDIUM 5.3 MEDIUM
HashiCorp Vault and Vault Enterprise 1.4.1 and newer allowed the enumeration of users via the LDAP auth method. Fixed in 1.5.6 and 1.6.1.
CVE-2020-25594 1 Hashicorp 1 Vault 2021-02-04 5.0 MEDIUM 5.3 MEDIUM
HashiCorp Vault and Vault Enterprise allowed for enumeration of Secrets Engine mount paths via unauthenticated HTTP requests. Fixed in 1.6.2 & 1.5.7.
CVE-2021-3024 1 Hashicorp 1 Vault 2021-02-04 5.0 MEDIUM 5.3 MEDIUM
HashiCorp Vault and Vault Enterprise disclosed the internal IP address of the Vault node when responding to some invalid, unauthenticated HTTP requests. Fixed in 1.6.2 & 1.5.7.
CVE-2020-10660 1 Hashicorp 1 Vault 2020-03-30 4.3 MEDIUM 5.3 MEDIUM
HashiCorp Vault and Vault Enterprise versions 0.9.0 through 1.3.3 may, under certain circumstances, have an Entity's Group membership inadvertently include Groups the Entity no longer has permissions to. Fixed in 1.3.4.