Skip to content
OpenAdvisories

Package · Ubuntu

consul

49 known vulnerabilities.

19 results · Clear filters · Feed

  • High 7.5

    Consul vulnerable to a denial of service in HTTP APIs

    HashiCorp Consul and Consul Enterprise are vulnerable to a denial of service in the HTTP API that may allow an unauthenticated attacker to exhaust memory on a Consul agent. This vulnerability (CVE-2026-105626) is fixed in Consul Community Edition 2.1.0 and Co…

  • High 8.8

    Consul vulnerable to an authorization bypass in service mesh registration

    HashiCorp Consul and Consul Enterprise are vulnerable to an authorization bypass in service mesh proxy registration. This may allow a user with service write permission to apply Envoy escape-hatch configuration without the required mesh write permission. This…

  • High 7.5

    Consul vulnerable to an authorization bypass in the agent's service mesh leaf certificate API

    HashiCorp Consul and Consul Enterprise 1.17.0 up to 2.0.4 are vulnerable to an authorization bypass in the agent's service mesh leaf certificate API that may allow an attacker without a valid ACL token to retrieve a cached service leaf certificate and its pri…

  • High 7.5

    Consul vulnerable to an authorization bypass in the Connect service mesh

    Consul and Consul Enterprise are vulnerable to an authorization bypass in the Connect service mesh that may allow a service to reach a destination it is not authorized to access. When building Envoy RBAC rules to enforce Connect intentions, Consul did not cor…

  • High 8.3

    Consul vulnerable to an authorization bypass in the catalog node-write path

    Consul and Consul Enterprise are vulnerable to an authorization bypass in the catalog node-write path that may allow an authenticated attacker to delete another node's catalog registration and take over its node identity. An attacker with a token granting nod…

  • High 7.5

    Unauthenticated denial of service via unbounded external gRPC connection acceptance

    Consul Community Edition and Consul Enterprise 1.13.0 through 2.0.2 are vulnerable to an unauthenticated denial of service through unbounded connection acceptance on the external gRPC listeners. A remote attacker may exhaust agent file descriptors, goroutines…

  • High 8.3

    Consul L7 Intentions Vulnerable To Headers Bypass

    A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using Headers in L7 traffic intentions could bypass HTTP header based access rules.

  • High 8.1
    CVE-2024-10005 Public exploit

    Consul L7 Intentions Vulnerable To URL Path Bypass

    A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using URL paths in L7 traffic intentions could bypass HTTP request path-based access rules.

  • High 8.7

    Consul Envoy Extension Downsteam Proxy Configuration By Upstream Service Owner

    Consul and Consul Enterprise allowed any user with service:write permissions to use Envoy extensions configured via service-defaults to patch remote proxy instances that target the configured service, regardless of whether the user has permission to modify th…

  • High 7.1

    HashiCorp Consul does not properly validate node or segment names prior to usage in JWT claim assertions

    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."

  • High 7.5

    Hashicorp Consul HTTP health check endpoints returning an HTTP redirect may be abused as SSRF vector

    HashiCorp Consul and Consul Enterprise up to 1.9.16, 1.10.9, and 1.11.4 may allow server side request forgery when the Consul client agent follows redirects returned by HTTP health check endpoints. Fixed in 1.9.17, 1.10.10, and 1.11.5.

  • High 8.8

    HashiCorp Consul Privilege Escalation Vulnerability

    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.

  • High 7.5

    HashiCorp Consul L7 deny intention results in an allow action

    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.

  • High 7.5

    Hashicorp Consul Missing SSL Certificate Validation

    HashiCorp Consul and Consul Enterprise 1.3.0 through 1.10.0 Envoy proxy TLS configuration does not validate destination service identity in the encoded subject alternative name. Fixed in 1.8.14, 1.9.8, and 1.10.1.

  • High 7.5

    Denial of service in HashiCorp Consul

    HashiCorp Consul Enterprise version 1.7.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.

  • High 7.5

    Allocation of Resources Without Limits or Throttling in Hashicorp Consul

    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.

  • High 7.5

    Denial of Service (DoS) in HashiCorp Consul

    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.

  • High 7.5

    HashiCorp Consul Incorrect Access Control vulnerability

    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.

  • High 7.4

    HashiCorp Consul vulnerable to Origin Validation Error

    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.