Hashicorp vulnerabilities
235 vulnerabilities
Known vulnerabilities in Hashicorp products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 27 products.
Products
27- Vault78 vulnerabilities
- Vault Enterprise49 vulnerabilities
- Consul48 vulnerabilities
- Nomad41 vulnerabilities
- Consul Enterprise23 vulnerabilities
- Nomad Enterprise23 vulnerabilities
- Tooling12 vulnerabilities
- Shared Library10 vulnerabilities
- Terraform Enterprise7 vulnerabilities
- Vagrant Vmware Fusion7 vulnerabilities
- Boundary6 vulnerabilities
- Go Getter6 vulnerabilities
- Terraform5 vulnerabilities
- Vagrant5 vulnerabilities
- Boundary Enterprise3 vulnerabilities
- Go Slug3 vulnerabilities
- Packer2 vulnerabilities
- Sentinel2 vulnerabilities
- Terraform Provider2 vulnerabilities
- Consul Docker Image1 vulnerabilities
- Consul Template1 vulnerabilities
- Hermes1 vulnerabilities
- Retryablehttp1 vulnerabilities
- Vagrant Vmware Utility1 vulnerabilities
- Vault Provider For Secrets Store Csi Driver1 vulnerabilities
- Vault Action1 vulnerabilities
- Vault Ssh Helper1 vulnerabilities
CVE-2018-19786hashicorpvault
EPSS score0.93%
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.CVE-2018-19653chainguardk3d+9EPSS score1.22%
HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication because the verify_outgoing setting is improperly documented. NOTE: the vendor has provided reconfiguration steps that do not require a software upgrade.CVE-2018-9057chainguardterraform-provider-aws+3EPSS score1.92%
aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0 has an inappropriate PRNG algorithm and seeding, which makes it easier for remote attackers to obtain access by leveraging an IAM account that was provisioned with a weak password.CVE-2018-15869debianpacker+15EPSS score1.80%
An Amazon Web Services (AWS) developer who does not specify the --owners flag when describing images via AWS CLI, and therefore not properly validating source software per AWS recommended security best practices, may unintentionally load an undesired and potentially malicious Amazon Machine Image (AMI) from the uncurated public community AMI catalog.CVE-2021-40862hashicorpterraform_enterpriseEPSS score0.97%
HashiCorp Terraform Enterprise up to v202108-1 contained an API endpoint that erroneously disclosed a sensitive URL to authenticated parties, which could be used for privilege escalation or unauthorized modification of a Terraform configuration. Fixed in v202109-1.CVE-2021-41802chainguardk3d+9EPSS score0.61%
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-41865ubuntunomad+1EPSS score0.97%
HashiCorp Nomad and Nomad Enterprise 1.1.1 through 1.1.5 allowed authenticated users with job submission capabilities to cause denial of service by submitting incomplete job specifications with a Consul mesh gateway and host networking mode. Fixed in 1.1.6.CVE-2021-41805ubuntuconsul+1EPSS score34.79%
HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4 has Incorrect Access Control. An ACL token (with the default operator:write permissions) in one namespace can be used for unintended privilege escalation in a different namespace.CVE-2021-41803debianconsul+3EPSS score1.07%
HashiCorp Consul 1.8.1 up to 1.11.8, 1.12.4, and 1.13.1 do not properly validate the node or segment names prior to interpolation and usage in JWT claim assertions with the auto config RPC. Fixed in 1.11.9, 1.12.5, and 1.13.2."CVE-2021-42135github.com/hashicorpvault+1EPSS score0.78%
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.CVE-2021-36213chainguardk3d+8EPSS score1.69%
HashiCorp Consul and Consul Enterprise 1.9.0 through 1.10.0 default deny policy with a single L7 application-aware intention deny action cancels out, causing the intention to incorrectly fail open, allowing L4 traffic. Fixed in 1.9.8 and 1.10.1.CVE-2021-36230chainguardterraform+17EPSS score0.95%
HashiCorp Terraform Enterprise releases up to v202106-1 did not properly perform authorization checks on a subset of API requests executed using the run token, allowing privilege escalation to organization owner. Fixed in v202107-1.CVE-2021-37218ubuntunomad+2EPSS score0.67%
HashiCorp Nomad and Nomad Enterprise Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.0.10 and 1.1.4.CVE-2021-37219chainguardk3d+9EPSS score1.15%
HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.8.15, 1.9.9 and 1.10.2.CVE-2021-43415ubuntunomad+2EPSS score1.22%
HashiCorp Nomad and Nomad Enterprise up to 1.0.13, 1.1.7, and 1.2.0, with the QEMU task driver enabled, allowed authenticated users with job submission capabilities to bypass the configured allowed image paths. Fixed in 1.0.14, 1.1.8, and 1.2.1.CVE-2021-43998github.com/hashicorpvault+1EPSS score1.04%
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-29653hashicorpvaultEPSS score0.55%
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.CVE-2021-27400hashicorpvaultEPSS score0.57%
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.1CVE-2021-27668hashicorpvaultEPSS score1.04%
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-2021-38554chainguardk3d+9EPSS score0.91%
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.