Skip to content

GHSA-496g-fr33-whrf BIT-consul-2020-25201 CVE-2020-25201 GO-2024-2501

Denial of service in HashiCorp Consul

High Go
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
2.61%
Chance of exploitation in the next 30 days. Higher than 85.41% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
CWE-834 Excessive Iteration
Fix
1.7.9
Upgrade github.com/hashicorp/consul to this version or later

Description

HashiCorp Consul Enterprise versions 1.7.0 up to 1.7.8 and 1.8.0 up to 1.8.4 includes a namespace replication bug which can be triggered to cause denial of service via infinite Raft writes. Fixed in 1.7.9 and 1.8.5.

Affected versions

Go

PackageVulnerableFixed in
github.com/hashicorp/consul
>= 1.7.0, < 1.7.9
1.7.9
github.com/hashicorp/consul
>= 1.8.0, < 1.8.5
1.8.5
github.com/hashicorp/consul
>= 1.7.0, < 1.7.9
>= 1.8.0, < 1.8.5
1.7.9
1.8.5

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/hashicorp/consul Go → 1.7.9

go
go get github.com/hashicorp/consul@v1.7.9 && go mod tidy

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-400: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How to prevent it
  • Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
  • Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
  • Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
  • Implementation: Ensure that all failures in resource allocation place the system into a safe posture.

CWE-834: Excessive Iteration

The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-cpfq-66p2-336j
Consul is vulnerable to arbitrary file read when configured with Kubernetes authentication
Medium Also affects github.com/hashicorp/consul
GHSA-qh7p-pfq3-677h
Consul event endpoint is vulnerable to denial of service
Medium Also affects github.com/hashicorp/consul
GHSA-7g3r-8c6v-hfmr
Consul key/value endpoint is vulnerable to denial of service
Medium Also affects github.com/hashicorp/consul
GHSA-99wr-c2px-grmh
Hashicorp Consul Cross-site Scripting vulnerability
Medium Also affects github.com/hashicorp/consul
GHSA-5c4w-8hhh-3c3h
Hashicorp Consul Improper Neutralization of HTTP Headers for Scripting Syntax vulnerability
Medium Also affects github.com/hashicorp/consul
GHSA-chgm-7r52-whjj
Hashicorp Consul Path Traversal vulnerability
Medium Also affects github.com/hashicorp/consul
GHSA-6m72-467w-94rh
Privilege Escalation in HashiCorp Consul
Medium Also affects github.com/hashicorp/consul
GHSA-9rhf-q362-77mx
Consul JWT Auth in L7 Intentions Allow for Mismatched Service Identity and JWT Providers
High Also affects github.com/hashicorp/consul
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor