VYPR

Bitnami package

vault

pkg:bitnami/vault

Vulnerabilities (79)

  • CVE-2025-6004MedAug 1, 2025
    affected >= 1.13.0, < 1.20.1fixed 1.20.1

    Vault and Vault Enterprise’s (“Vault”) user lockout feature could be bypassed for Userpass and LDAP authentication methods. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

  • CVE-2025-6000CriAug 1, 2025
    affected >= 0.8.0, < 1.20.1fixed 1.20.1

    A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution on the underlying host if a plugin directory is set in Vault’s configuration. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.1

  • CVE-2025-5999HigAug 1, 2025
    affected >= 0.10.4, < 1.20.0fixed 1.20.0

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

  • CVE-2025-4656LowJun 25, 2025
    affected >= 1.14.8, < 1.20.0fixed 1.20.0

    Vault Community and Vault Enterprise rekey and recovery key operations can lead to a denial of service due to uncontrolled cancellation by a Vault operator. This vulnerability (CVE-2025-4656) has been remediated in Vault Community Edition 1.20.0 and Vault Enterprise 1.20.0, 1.19.

  • CVE-2025-3879MedMay 2, 2025
    affected >= 0.10.0, < 1.19.1fixed 1.19.1

    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 Vault Enterprise 1.19.1, 1.18.7,

  • CVE-2025-4166MedMay 2, 2025
    affected >= 0.3.0, < 1.19.3fixed 1.19.3

    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. This vulnerability, identified a

  • CVE-2024-8185HigOct 31, 2024
    affected >= 1.2.0, < 1.18.1fixed 1.18.1

    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 volume of requests to the endpoint

  • CVE-2024-9180HigOct 10, 2024
    affected >= 1.7.7, < 1.18.0fixed 1.18.0

    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.16.11, and 1.15.16.

  • CVE-2024-7594HigSep 26, 2024
    affected >= 1.7.7, < 1.17.6fixed 1.17.6

    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 user to Vault’s SSH secrets engin

  • CVE-2024-8365MedSep 2, 2024
    affected >= 1.16.7, < 1.16.9fixed 1.16.9

    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 of client tokens and token ac

  • CVE-2024-6468HigJul 11, 2024
    affected >= 1.10.0, < 1.16.3fixed 1.16.3

    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 listed in proxy_protocol_auth

  • CVE-2024-5798LowJun 12, 2024
    affected >= 0.11.0, < 1.16.2fixed 1.16.2

    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 an invalid login to succeed whe

  • CVE-2024-2877MedApr 30, 2024
    affected >= 1.15.0, < 1.15.8fixed 1.15.8

    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 vulnerability, CVE-2024-2877, was fixed

  • CVE-2024-2660MedApr 4, 2024
    affected >= 1.14.0, < 1.16.0fixed 1.16.0

    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 Vault 1.16.0 and Vault Enterpri

  • CVE-2024-2048HigMar 4, 2024
    affected >= 1.15.5, < 1.16.0fixed 1.16.0

    Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as trusted certificate. In this configuration, an attacker may be able to craft a malicious certificate that could be used to

  • CVE-2024-0831MedFeb 1, 2024
    affected >= 1.15.0, < 1.15.5fixed 1.15.5

    Vault and Vault Enterprise (“Vault”) may expose sensitive information when enabling an audit device which specifies the `log_raw` option, which may log sensitive information to other audit devices, regardless of whether they are configured to use `log_raw`.

  • CVE-2023-6337HigDec 8, 2023
    affected >= 1.13.0, < 1.13.12fixed 1.13.12

    HashiCorp Vault and Vault Enterprise 1.12.0 and newer are vulnerable to a denial of service through memory exhaustion of the host when handling large unauthenticated and authenticated HTTP requests from a client. Vault will attempt to map the request to memory, resulting in the e

  • CVE-2023-5954MedNov 9, 2023
    affected >= 1.13.7, < 1.13.10fixed 1.13.10

    HashiCorp Vault and Vault Enterprise inbound client requests triggering a policy check can lead to an unbounded consumption of memory. A large number of these requests may lead to denial-of-service. Fixed in Vault 1.15.2, 1.14.6, and 1.13.10.

  • CVE-2023-5077HigSep 29, 2023
    affected >= 0.10.0, < 1.13.0fixed 1.13.0

    The Vault and Vault Enterprise ("Vault") Google Cloud secrets engine did not preserve existing Google Cloud IAM Conditions upon creating or updating rolesets. Fixed in Vault 1.13.0.

  • CVE-2023-3775MedSep 29, 2023
    affected >= 0.11.0, < 1.13.8fixed 1.13.8

    A Vault Enterprise Sentinel Role Governing Policy created by an operator to restrict access to resources in one namespace can be applied to requests outside in another non-descendant namespace, potentially resulting in denial of service. Fixed in Vault Enterprise 1.15.0, 1.14.4,