Skip to content
OpenAdvisories

Vendor

HashiCorp

142 known vulnerabilities.

70 results · Clear filters · Feed

  • Medium 6.5

    Nomad Allocations Vulnerable To Privilege Escalation Within A Namespace Using Unredacted Workload Identity Tokens

    Nomad Community and Nomad Enterprise ("Nomad") allocations are vulnerable to privilege escalation within a namespace through unredacted workload identity tokens. This vulnerability, identified as CVE-2024-12678, is fixed in Nomad Community Edition 1.9.4 and N…

  • Medium 5.9

    Boundary Controller Incorrectly Handles HTTP Requests On Initialization Which May Lead to a Denial of Service

    Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the initialization of the Boundary controller, which may cause the Boundary server to terminate prematurely. Boundary is only vulnerable to this flaw durin…

  • Medium 6.1

    Consul Vulnerable To Reflected XSS On Content-Type Error Manipulation

    A vulnerability was identified in Consul and Consul Enterprise such that the server response did not explicitly set a Content-Type HTTP header, allowing user-provided inputs to be misinterpreted and lead to reflected XSS.

  • Medium 6.2

    Vault Leaks AppRole Client Tokens And Accessor in Audit Log

    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 clien…

  • Medium 5.8

    Nomad Vulnerable to Allocation Directory Escape On Non-Existing File Paths Through Archive Unpacking

    In HashiCorp Nomad and Nomad Enterprise from 0.6.1 up to 1.6.13, 1.7.10, and 1.8.2, the archive unpacking process is vulnerable to writes outside the allocation directory during migration of allocation directories when multiple archive headers target the same…

  • Medium 6.0

    go-retryablehttp can leak basic auth credentials to log files

    go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.

  • Medium 5.5

    Vault Enterprise Leaks Sensitive HTTP Request Headers in the Audit Log When Deployed With a Performance Standby Node

    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-2…

  • Medium 6.4

    Vault TLS Cert Auth Method Did Not Correctly Validate OCSP Responses

    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…

  • Medium 4.5

    Vault May Expose Sensitive Information When Configuring An Audit Log Device

    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`.

  • Medium 5.9

    Vault Requests Triggering Policy Checks May Lead To Unbounded Memory Consumption

    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.

  • Medium 4.2

    Vault Enterprise's Sentinel RGP Policies Allowed For Cross-Namespace Denial of Service

    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 Enterp…

  • Medium 6.8

    Vault's Transit Secrets Engine Allowed Nonce Specified without Convergent Encryption

    HashiCorp Vault and Vault Enterprise transit secrets engine allowed authorized users to specify arbitrary nonces, even with convergent encryption disabled. The encrypt endpoint, in combination with an offline attack, could be used to decrypt arbitrary ciphert…

  • Medium 6.3

    Terraform Allows Arbitrary File Write During Init Operation

    Terraform version 1.0.8 through 1.5.6 allows arbitrary file write during the `init` operation if run on maliciously crafted Terraform configuration. This vulnerability is fixed in Terraform 1.5.7.

  • Medium 5.3

    Vault's LDAP Auth Method Allows for User Enumeration

    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…

  • Medium 4.9

    Vault Enterprise Namespace Creation May Lead to Denial of Service

    An unhandled error in Vault Enterprise's namespace creation may cause the Vault process to crash, potentially resulting in denial of service. Fixed in 1.14.1, 1.13.5, and 1.12.9.

  • Medium 5.3

    Nomad Search API Leaks Information About CSI Plugins

    HashiCorp Nomad and Nomad Enterprise 0.11.0 up to 1.5.6 and 1.4.1 HTTP search API can reveal names of available CSI plugins to unauthenticated users or users without the plugin:read policy. Fixed in 1.6.0, 1.5.7, and 1.4.1.

  • Medium 4.1

    Nomad ACL Policies without Label are Applied to Unexpected Resources

    HashiCorp Nomad and Nomad Enterprise 0.7.0 up to 1.5.6 and 1.4.10 ACL policies using a block without a label generates unexpected results. Fixed in 1.6.0, 1.5.7, and 1.4.11.

  • Medium 5.0

    Terraform Enterprise Agent Pool Controls Allowed Unauthorized Workspaces To Target an Agent Pool

    Terraform Enterprise since v202207-1 did not properly implement authorization rules for agent pools, allowing the workspace to be targeted by unauthorized agents. This authorization flaw could potentially allow a workspace to access resources from a separate,…

  • Medium 4.3

    Vault’s KV Diff Viewer Allowed for HTML Injection

    Vault and Vault Enterprise's (Vault) key-value v2 (kv-v2) diff viewer allowed HTML injection into the Vault web UI through key values. This vulnerability, CVE-2023-2121, is fixed in Vault 1.14.0, 1.13.3, 1.12.7, and 1.11.11.

  • Medium 4.9

    Consul Cluster Peering can Result in Denial of Service

    Consul and Consul Enterprise's cluster peering implementation contained a flaw whereby a peer cluster with service of the same name as a local service could corrupt Consul state, resulting in denial of service. This vulnerability was resolved in Consul 1.14.5…

  • Medium 6.5

    Vault Vulnerable to SQL Injection When Configuring the Microsoft SQL Database Storage Backend

    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 s…

  • Medium 6.5

    Vault PKI Issuer Endpoint Did Not Correctly Authorize Access to Issuer Metadata

    HashiCorp Vault's PKI mount issuer endpoints did not correctly authorize access to remove an issuer or modify issuer metadata, potentially resulting in denial of service of the PKI mount. This bug did not affect public or private key material, trust chains or…

  • Medium 5.0

    Vault Vulnerable to Cache-Timing Attacks During Seal and Unseal Operations

    HashiCorp Vault's implementation of Shamir's secret sharing used precomputed table lookups, and was vulnerable to cache-timing attacks. An attacker with access to, and the ability to observe a large number of unseal operations on the host through a side chann…

  • Medium 4.4

    Vault Fails to Verify if the AppRole SecretID Belongs to Role During a Destroy Operation

    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…

  • Medium 4.9

    Consul Server Panic when Ingress and API Gateways Configured with Peering

    Consul and Consul Enterprise allowed an authenticated user with service:write permissions to trigger a workflow that causes Consul server and client agents to crash under certain circumstances. This vulnerability was fixed in Consul 1.14.5.

  • Medium 6.5

    Nomad Client Vulnerable to Decompression Bombs in Artifact Block

    HashiCorp Nomad and Nomad Enterprise 1.2.15 up to 1.3.8, and 1.4.3 jobs using a maliciously compressed artifact stanza source can cause excessive disk usage. Fixed in 1.2.16, 1.3.9, and 1.4.4.

  • Medium 4.2

    Go-Getter Vulnerable to Decompression Bombs

    HashiCorp go-getter up to 1.6.2 and 2.1.1 is vulnerable to decompression bombs. Fixed in 1.7.0 and 2.2.0.

  • Medium 5.0

    Boundary Workers Store Rotated Credentials in Plaintext Even When a Key Management Service Configured

    HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key Management Service (KMS) defined in the configuration file, new credentials created after an automatic rotation may not have been encrypted via the i…

  • Medium 5.3

    Consul Peering Imported Nodes/Services Leak

    HashiCorp Consul and Consul Enterprise 1.13.0 up to 1.13.3 do not filter cluster filtering's imported nodes and services for HTTP or RPC endpoints used by the UI. Fixed in 1.14.0.

  • Medium 5.0

    Nomad Workload Identity Token Can List Non-sensitive Metadata for Paths Under nomad/

    HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.4.1 workload identity token can list non-sensitive metadata for paths under nomad/ that belong to other jobs in the same namespace. Fixed in 1.4.2.