GHSA-q2qr-3c2p-9235 BIT-consul-2020-12758 CVE-2020-12758 GO-2022-0861
Denial of Service (DoS) in HashiCorp Consul
Medium
Go
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 1.71%
- Chance of exploitation in the next 30 days. Higher than 77.33% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
1.6.6- Upgrade github.com/hashicorp/consul to this version or later
Description
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.
Specific Go Packages Affected
github.com/hashicorp/consul/agent/consul/discoverychain
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/hashicorp/consul | >= 1.6.0-beta1, < 1.6.6 |
1.6.6 |
| github.com/hashicorp/consul | >= 1.7.0, < 1.7.4 |
1.7.4 |
| github.com/hashicorp/consul | >= 1.6.0-beta1, < 1.6.6>= 1.7.0, < 1.7.4 |
1.6.61.7.4 |
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.6.6
- go
go get github.com/hashicorp/consul@v1.6.6 && go mod tidy
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
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.
References
Advisories
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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-496g-fr33-whrf Denial of service in HashiCorp Consul | High | Also affects github.com/hashicorp/consul |
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