Consul and Consul Enterprises 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, and 1.15.3
The product releases a resource that is still intended to be used by itself or another actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Consul | Hashicorp | 1.13.0 (including) | 1.14.7 (excluding) |
| Consul | Hashicorp | 1.15.0 (including) | 1.15.3 (excluding) |
| Consul | Ubuntu | bionic | * |
| Consul | Ubuntu | kinetic | * |
| Consul | Ubuntu | mantic | * |
| Consul | Ubuntu | trusty | * |
| Consul | Ubuntu | xenial | * |
This weakness focuses on errors in which the product should not release a resource, but performs the release anyway. This is different than a weakness in which the product releases a resource at the appropriate time, but it maintains a reference to the resource, which it later accesses. For this weakness, the resource should still be valid upon the subsequent access. When a product releases a resource that is still being used, it is possible that operations will still be taken on this resource, which may have been repurposed in the meantime, leading to issues similar to CWE-825. Consequences may include denial of service, information exposure, or code execution.