Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,384
Published in 7 days
1,885
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “HashiCorp Vault”

83 vulnerabilities
  1. Medium 6.7

    CVE-2023-0620 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise versions 0.8.0 through 1.13.1 are vulnerable to an SQL injection attack when configuring the Microsoft SQL (MSSQL) Database Storage Backend. When configuring the MSSQL plugin through the local, certain parameters are not sanitized when passed to the user-provided MSSQL database. An attacker may modify these parameters to execute a malicious SQL command. This…

    Published 30 Mar 2023 · Fixed in 1.11.9, 1.12.5, 1.13.1 · NVD
  2. High 8.1

    CVE-2023-24999 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise’s approle auth method allowed any authenticated user with access to an approle destroy endpoint to destroy the secret ID of any other role by providing the secret ID accessor. This vulnerability is fixed in Vault 1.13.0, 1.12.4, 1.11.8, 1.10.11 and above.

    Published 11 Mar 2023 · Fixed in 1.10.11, 1.11.8, 1.12.4 · NVD
  3. Medium 5.3

    CVE-2022-41316 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's CA into memory on startup, resulting in the revocation list not being checked if the CRL has not yet been retrieved. Fixed in 1.12.0, 1.11.4, 1.10.7, and 1.9.10.

    Published 12 Oct 2022 · Fixed in 1.9.10, 1.10.7, 1.11.4 · NVD
  4. Critical 9.1

    CVE-2022-40186 · HashiCorp Vault

    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…

    Published 22 Sept 2022 · Fixed in 1.9.9, 1.10.6, 1.11.3 · NVD
  5. Critical 9.1

    CVE-2022-36129 · HashiCorp Vault

    HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint that could be abused to override the voter status of a node within a Vault HA cluster, introducing potential for future data loss or catastrophic failure. Fixed in Vault Enterprise 1.9.8, 1.10.5, and 1.11.1.

    Published 26 Jul 2022 · NVD
  6. Medium 5.3

    CVE-2022-30689 · HashiCorp Vault

    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.

    Published 17 May 2022 · Fixed in 1.10.3 · NVD
  7. Medium 6.5

    CVE-2022-25244 · HashiCorp Vault

    Vault Enterprise clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration endpoint to authorized operators with `read` permissions on this endpoint. Fixed in Vault Enterprise 1.9.4, 1.8.9 and 1.7.10.

    Published 10 Mar 2022 · Fixed in 1.7.10, 1.8.9, 1.9.4 · NVD
  8. Medium 6.5

    CVE-2022-25243 · HashiCorp Vault

    "Vault and Vault Enterprise 1.8.0 through 1.8.8, and 1.9.3 allowed the PKI secrets engine under certain configurations to issue wildcard certificates to authorized users for a specified domain, even if the PKI role policy attribute allow_subdomains is set to false. Fixed in Vault Enterprise 1.8.9 and 1.9.4.

    Published 10 Mar 2022 · Fixed in 1.8.9, 1.9.4 · NVD
  9. Medium 4.9

    CVE-2021-45042 · HashiCorp Vault

    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.

    Published 17 Dec 2021 · Fixed in 1.7.7, 1.8.6 · NVD
  10. Medium 6.5

    CVE-2021-43998 · HashiCorp Vault

    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.

    Published 30 Nov 2021 · NVD
  11. High 8.1

    CVE-2021-42135 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise 1.8.x through 1.8.4 may have an unexpected interaction between glob-related policies and the Google Cloud secrets engine. Users may, in some situations, have more privileges than intended, e.g., a user with read permission for the /gcp/roleset/* path may be able to issue Google Cloud service account credentials.

    Published 11 Oct 2021 · NVD
  12. Medium 5.4

    CVE-2021-41802 · HashiCorp Vault

    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.

    Published 8 Oct 2021 · Fixed in 1.7.5, 1.8.4 · NVD
  13. Medium 5.3

    CVE-2021-27668 · HashiCorp Vault

    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.

    Published 31 Aug 2021 · Fixed in 1.6.3 · NVD
  14. Medium 5.3

    CVE-2021-38554 · HashiCorp Vault

    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.

    Published 13 Aug 2021 · Fixed in 1.8.0 · NVD
  15. Medium 4.4

    CVE-2021-38553 · HashiCorp Vault

    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.

    Published 13 Aug 2021 · Fixed in 1.8.0 · NVD
  16. High 7.4

    CVE-2021-32923 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.

    Published 3 Jun 2021 · Fixed in 1.5.9, 1.6.5, 1.7.2 · NVD
  17. High 7.5

    CVE-2021-29653 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise 1.5.1 and newer, under certain circumstances, may exclude revoked but unexpired certificates from the CRL. Fixed in 1.5.8, 1.6.4, and 1.7.1.

    Published 22 Apr 2021 · Fixed in 1.5.8, 1.6.4, 1.7.1 · NVD
  18. High 7.5

    CVE-2021-27400 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise Cassandra integrations (storage backend and database secrets engine plugin) did not validate TLS certificates when connecting to Cassandra clusters. Fixed in 1.6.4 and 1.7.1

    Published 22 Apr 2021 · Fixed in 1.6.4, 1.7.1 · NVD
  19. High 7.5

    CVE-2021-3282 · HashiCorp Vault

    HashiCorp Vault Enterprise 1.6.0 & 1.6.1 allowed the `remove-peer` raft operator command to be executed against DR secondaries without authentication. Fixed in 1.6.2.

    Published 1 Feb 2021 · NVD
  20. Medium 5.3

    CVE-2021-3024 · HashiCorp Vault

    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.

    Published 1 Feb 2021 · Fixed in 1.5.7, 1.6.2 · NVD
  21. Medium 5.3

    CVE-2020-25594 · HashiCorp Vault

    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.

    Published 1 Feb 2021 · Fixed in 1.5.7, 1.6.2 · NVD
  22. Medium 5.3

    CVE-2020-35453 · HashiCorp Vault

    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.

    Published 17 Dec 2020 · Fixed in 1.5.6, 1.6.1 · NVD
  23. Medium 5.3

    CVE-2020-35177 · HashiCorp Vault

    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.

    Published 17 Dec 2020 · Fixed in 1.5.6, 1.6.1 · NVD
  24. Critical 9.8

    CVE-2020-35192 · HashiCorp Vault

    The official vault docker images before 0.11.6 contain a blank password for a root user. System using the vault docker container deployed by affected versions of the docker image may allow a remote attacker to achieve root access with a blank password.

    Published 17 Dec 2020 · Fixed in 0.11.6 · NVD
  25. Medium 6.8

    CVE-2020-25816 · HashiCorp Vault

    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.

    Published 30 Sept 2020 · Fixed in 1.4.7, 1.5.4 · NVD
  26. High 8.2

    CVE-2020-16251 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise versions 0.8.3 and newer, when configured with the GCP GCE auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1.

    Published 26 Aug 2020 · Fixed in 1.3.8, 1.4.4, 1.5.1 · NVD
  27. High 8.2

    CVE-2020-16250 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise versions 0.7.1 and newer, when configured with the AWS IAM auth method, may be vulnerable to authentication bypass. Fixed in 1.2.5, 1.3.8, 1.4.4, and 1.5.1..

    Published 26 Aug 2020 · Fixed in 1.3.8, 1.4.4, 1.5.1 · NVD
  28. High 7.5

    CVE-2020-13223 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise logged proxy environment variables that potentially included sensitive credentials. Fixed in 1.3.6 and 1.4.2.

    Published 10 Jun 2020 · Fixed in 1.3.6, 1.4.2 · NVD
  29. Critical 9.8

    CVE-2020-12757 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials with the default time-to-live lease duration instead of the engine-configured setting. This may lead to generated GCP credentials being valid for longer than intended. Fixed in 1.4.2.

    Published 10 Jun 2020 · Fixed in 1.4.2 · NVD
  30. Critical 9.1

    CVE-2020-10661 · HashiCorp Vault

    HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may, under certain circumstances, have existing nested-path policies grant access to Namespaces created after-the-fact. Fixed in 1.3.4.

    Published 23 Mar 2020 · NVD
  31. Medium 5.3

    CVE-2020-10660 · HashiCorp Vault

    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.

    Published 23 Mar 2020 · NVD
  32. High 7.5

    CVE-2020-7220 · HashiCorp Vault

    HashiCorp Vault Enterprise 0.11.0 through 1.3.1 fails, in certain circumstances, to revoke dynamic secrets for a mount in a deleted namespace. Fixed in 1.3.2.

    Published 23 Jan 2020 · Fixed in 1.3.2 · NVD
  33. High 8.1

    CVE-2018-19786 · HashiCorp Vault

    HashiCorp Vault before 1.0.0 writes the master key to the server log in certain unusual or misconfigured scenarios in which incorrect data comes from the autoseal mechanism without an error being reported.

    Published 5 Dec 2018 · Fixed in 1.0.0 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.