HashiCorp HashiCorp

stack.watch can notify you when security vulnerabilities are reported in any HashiCorp product. You can add multiple products that you use with HashiCorp to create your own personal software stack watcher.

Products by HashiCorp Sorted by Most Security Vulnerabilities since 2018

HashiCorp Consul10 vulnerabilities

HashiCorp Vault6 vulnerabilities

HashiCorp Nomad4 vulnerabilities

HashiCorp Terraform2 vulnerabilities

HashiCorp Packer1 vulnerability

HashiCorp Sentinel1 vulnerability

@HashiCorp Tweets

Check out this list of helpful #Packer tips and tricks for those who are looking to sharpen their image management… https://t.co/9AyFdG6Mio
Wed Jul 08 01:44:00 +0000 2020

Here's a #Terraform 0.13 feature you might not have noticed: Custom variable validation will be production ready af… https://t.co/q1mNBIu0kY
Tue Jul 07 19:10:02 +0000 2020

In this #HashiConf presentation, @vizionr shows how @criteo runs Consul at scale—its environment includes 4 operato… https://t.co/qAfFy9ngi7
Tue Jul 07 16:19:01 +0000 2020

The ability to use the 'depends_on' meta-argument for #Terraform modules was one of the most requested features for… https://t.co/h8CyQajJfV
Tue Jul 07 14:45:07 +0000 2020

See the latest optimizations @criteo made to get the most out of HashiCorp #Consul running at high scale in this… https://t.co/TQR8kQK271
Tue Jul 07 08:12:00 +0000 2020

By the Year

In 2020 there have been 15 vulnerabilities in HashiCorp with an average score of 7.3 out of ten. Last year HashiCorp had 5 security vulnerabilities published. That is, 10 more vulnerabilities have already been reported in 2020 as compared to last year. Last year, the average CVE base score was greater by 0.73

Year Vulnerabilities Average Score
2020 15 7.33
2019 5 8.06
2018 4 7.28

It may take a day or so for new HashiCorp vulnerabilities to show up. Additionally vulnerabilities may be tagged under a different product or component name.

Latest HashiCorp Security Vulnerabilities

HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry

CVE-2020-12758 7.5 - High - June 11, 2020

HashiCorp Consul and Consul Enterprise could crash when configured with an abnormally-formed service-router entry. Introduced in 1.6.0, fixed in 1.6.6 and 1.7.4.

Improper Resource Shutdown or Release

HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers

CVE-2020-12797 5.3 - Medium - June 11, 2020

HashiCorp Consul and Consul Enterprise failed to enforce changes to legacy ACL token rules due to non-propagation to secondary data centers. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

Incorrect Permission Assignment for Critical Resource

HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center

CVE-2020-13170 7.5 - High - June 11, 2020

HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4.

Improper Input Validation

HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature

CVE-2020-13250 7.5 - High - June 11, 2020

HashiCorp Consul and Consul Enterprise include an HTTP API (introduced in 1.2.0) and DNS (introduced in 1.4.3) caching feature that was vulnerable to denial of service. Fixed in 1.6.6 and 1.7.4.

Memory Corruption

HashiCorp Vault and Vault Enterprise before 1.3.6

CVE-2020-13223 7.5 - High - June 10, 2020

HashiCorp Vault and Vault Enterprise before 1.3.6, and 1.4.2 before 1.4.2, insert Sensitive Information into a Log File.

Information Leak

HashiCorp Vault and Vault Enterprise 1.4.x before 1.4.2 has Incorrect Access Control.

CVE-2020-12757 9.8 - Critical - June 10, 2020

HashiCorp Vault and Vault Enterprise 1.4.x before 1.4.2 has Incorrect Access Control.

Improper Privilege Management

HashiCorp Nomad and Nomad Enterprise up to 0.10.4 contained a cross-site scripting vulnerability such

CVE-2020-10944 5.4 - Medium - April 28, 2020

HashiCorp Nomad and Nomad Enterprise up to 0.10.4 contained a cross-site scripting vulnerability such that files from a malicious workload could cause arbitrary JavaScript to execute in the web UI. Fixed in 0.10.5.

XSS

HashiCorp Vault and Vault Enterprise versions 0.9.0 through 1.3.3 may

CVE-2020-10660 5.3 - Medium - March 23, 2020

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.

Incorrect Default Permissions

HashiCorp Vault and Vault Enterprise versions 0.11.0 through 1.3.3 may

CVE-2020-10661 9.1 - Critical - March 23, 2020

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.

HashiCorp Sentinel up to 0.10.1 incorrectly parsed negation in certain policy expressions

CVE-2019-19879 7.5 - High - February 14, 2020

HashiCorp Sentinel up to 0.10.1 incorrectly parsed negation in certain policy expressions. Fixed in 0.10.2.

HashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services

CVE-2020-7219 7.5 - High - January 31, 2020

HashiCorp Consul and Consul Enterprise up to 1.6.2 HTTP/RPC services allowed unbounded resource usage, and were susceptible to unauthenticated denial of service. Fixed in 1.6.3.

Uncontrolled Resource Consumption ('Resource Exhaustion')

HashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints

CVE-2020-7955 5.3 - Medium - January 31, 2020

HashiCorp Consul and Consul Enterprise 1.4.1 through 1.6.2 did not uniformly enforce ACLs across all API endpoints, resulting in potential unintended information disclosure. Fixed in 1.6.3.

Information Leak

HashiCorp Nomad and Nomad Enterprise before 0.10.3

CVE-2020-7218 7.5 - High - January 31, 2020

HashiCorp Nomad and Nomad Enterprise before 0.10.3 allow unbounded resource usage.

Uncontrolled Resource Consumption ('Resource Exhaustion')

HashiCorp Nomad and Nomad Enterprise up to 0.10.2 incorrectly validated role/region associated with TLS certificates used for mTLS RPC

CVE-2020-7956 9.8 - Critical - January 31, 2020

HashiCorp Nomad and Nomad Enterprise up to 0.10.2 incorrectly validated role/region associated with TLS certificates used for mTLS RPC, and were susceptible to privilege escalation. Fixed in 0.10.3.

Improper Certificate Validation

HashiCorp Vault Enterprise 0.11.0 through 1.3.1 fails

CVE-2020-7220 7.5 - High - January 23, 2020

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.

Information Leak

When using the Azure backend with a shared access signature (SAS)

CVE-2019-19316 7.5 - High - December 02, 2019

When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP.

Use of a Broken or Risky Cryptographic Algorithm

HashiCorp Nomad 0.9.0 through 0.9.1 has Incorrect Access Control

CVE-2019-12618 9.8 - Critical - August 12, 2019

HashiCorp Nomad 0.9.0 through 0.9.1 has Incorrect Access Control via the exec driver.

Authorization

HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control

CVE-2019-12291 7.5 - High - June 06, 2019

HashiCorp Consul 1.4.0 through 1.5.0 has Incorrect Access Control. Keys not matching a specific ACL rule used for prefix matching in a policy can be deleted by a token using that policy even with default deny settings configured.

Authorization

HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication

CVE-2019-9764 7.4 - High - March 26, 2019

HashiCorp Consul 1.4.3 lacks server hostname verification for agent-to-agent TLS communication. In other words, the product behaves as if verify_server_hostname were set to false, even when it is actually set to true. This is fixed in 1.4.4.

Security Features

HashiCorp Consul (and Consul Enterprise) 1.4.x before 1.4.3

CVE-2019-8336 8.1 - High - March 05, 2019

HashiCorp Consul (and Consul Enterprise) 1.4.x before 1.4.3 allows a client to bypass intended access restrictions and obtain the privileges of one other arbitrary token within secondary datacenters, because a token with literally "<hidden>" as its secret is used in unusual circumstances.

Permissions, Privileges, and Access Controls

HashiCorp Consul 0.5.1 through 1.4.0 can use cleartext agent-to-agent RPC communication

CVE-2018-19653 5.9 - Medium - December 09, 2018

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.

Cryptographic Issues

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

CVE-2018-19786 8.1 - High - December 05, 2018

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.

Information Exposure Through Log Files

An Amazon Web Services (AWS) developer who does not specify the --owners flag when describing images

CVE-2018-15869 5.3 - Medium - August 25, 2018

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.

Incorrect Permission Assignment for Critical Resource

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

CVE-2018-9057 9.8 - Critical - March 27, 2018

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.

Insufficient Entropy in PRNG

Built by Foundeo Inc., with data from the National Vulnerability Database (NVD), Icons by Icons8