Hashicorp

Vault

66 Schwachstellen gefunden.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.05%
  • Veröffentlicht 02.05.2025 16:15:10
  • Zuletzt bearbeitet 12.08.2025 01:39:23

Vault Community, Vault Enterprise (“Vault”) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Va...

  • EPSS 0.01%
  • Veröffentlicht 02.05.2025 14:57:58
  • Zuletzt bearbeitet 12.08.2025 01:44:28

Vault Community and Vault Enterprise Key/Value (kv) Version 2 plugin may unintentionally expose sensitive information in server and audit logs when users submit malformed payloads during secret creation or update operations via the Vault REST API. Th...

  • EPSS 0.55%
  • Veröffentlicht 31.10.2024 16:15:06
  • Zuletzt bearbeitet 07.08.2025 19:14:38

Vault Community and Vault Enterprise (“Vault”) clusters using Vault’s Integrated Storage backend are vulnerable to a denial-of-service (DoS) attack through memory exhaustion through a Raft cluster join API endpoint . An attacker may send a large volu...

  • EPSS 0.27%
  • Veröffentlicht 10.10.2024 21:15:05
  • Zuletzt bearbeitet 18.10.2024 20:15:03

A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s privileges to Vault’s root policy. Fixed in Vault Community Edition 1.18.0 and Vault Enterprise 1.18.0, 1.17.7, 1....

  • EPSS 0.2%
  • Veröffentlicht 26.09.2024 20:15:07
  • Zuletzt bearbeitet 08.08.2025 01:47:11

Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized use...

  • EPSS 0.09%
  • Veröffentlicht 02.09.2024 05:15:17
  • Zuletzt bearbeitet 04.09.2024 14:37:03

Vault Community Edition and Vault Enterprise experienced a regression where functionality that HMAC’d sensitive headers in the configured audit device, specifically client tokens and token accessors, was removed. This resulted in the plaintext values...

  • EPSS 0.4%
  • Veröffentlicht 11.07.2024 21:15:12
  • Zuletzt bearbeitet 13.08.2025 14:01:26

Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not...

  • EPSS 0.22%
  • Veröffentlicht 12.06.2024 19:15:51
  • Zuletzt bearbeitet 07.08.2025 16:56:44

Vault and Vault Enterprise did not properly validate the JSON Web Token (JWT) role-bound audience claim when using the Vault JWT auth method. This may have resulted in Vault validating a JWT the audience and role-bound claims do not match, allowing a...

  • EPSS 0.06%
  • Veröffentlicht 30.04.2024 15:15:52
  • Zuletzt bearbeitet 08.08.2025 18:45:12

Vault Enterprise, when configured with performance standby nodes and a configured audit device, will inadvertently log request headers on the standby node. These logs may have included sensitive HTTP request information in cleartext. This vulnerabil...

  • EPSS 0.16%
  • Veröffentlicht 04.04.2024 18:15:14
  • Zuletzt bearbeitet 08.08.2025 19:00:18

Vault and Vault Enterprise TLS certificates auth method did not correctly validate OCSP responses when one or more OCSP sources were configured. This vulnerability, CVE-2024-2660, affects Vault and Vault Enterprise 1.14.0 and above, and is fixed in V...