Skip to content

HashiCorp Consul vulnerable to authorization bypass

Moderate severity GitHub Reviewed Published Sep 25, 2022 to the GitHub Advisory Database • Updated Sep 6, 2023

Package

gomod github.com/hashicorp/consul (Go)

Affected versions

< 1.11.9
>= 1.12.0, < 1.12.5
>= 1.13.0, < 1.13.2

Patched versions

1.11.9
1.12.5
1.13.2

Description

HashiCorp Consul and Consul Enterprise versions prior to 1.11.9, 1.12.5, and 1.13.2 do not check for multiple SAN URI values in a CSR on the internal RPC endpoint, enabling leverage of privileged access to bypass service mesh intentions. A specially crafted CSR sent directly to Consul’s internal server agent RPC endpoint can include multiple SAN URI values with additional service names. This issue has been fixed in versions 1.11.9, 1.12.5, and 1.13.2. There are no known workarounds.

References

Published by the National Vulnerability Database Sep 23, 2022
Published to the GitHub Advisory Database Sep 25, 2022
Reviewed Sep 29, 2022
Last updated Sep 6, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.117%
(47th percentile)

Weaknesses

CVE ID

CVE-2022-40716

GHSA ID

GHSA-m69r-9g56-7mv8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.