Skip to content

Hashicorp Vault vulnerable to Improper Check or Handling of Exceptional Conditions

High severity GitHub Reviewed Published Jul 11, 2024 to the GitHub Advisory Database • Updated Sep 6, 2024

Package

gomod github.com/hashicorp/vault (Go)

Affected versions

>= 1.16.0-rc1, < 1.16.3
>= 1.17.0-rc1, < 1.17.2
>= 1.10.0, < 1.15.12

Patched versions

1.16.3
1.17.2
1.15.12

Description

Vault and Vault Enterprise did not properly handle requests originating from unauthorized IP addresses when the TCP listener option, proxy_protocol_behavior, was set to deny_unauthorized. When receiving a request from a source IP address that was not listed in proxy_protocol_authorized_addrs, the Vault API server would shut down and no longer respond to any HTTP requests, potentially resulting in denial of service.

While this bug also affected versions of Vault up to 1.17.1 and 1.16.5, a separate regression in those release series did not allow Vault operators to configure the deny_unauthorized option, thus not allowing the conditions for the denial of service to occur.

Fixed in Vault and Vault Enterprise 1.17.2, 1.16.6, and 1.15.12

References

Published by the National Vulnerability Database Jul 11, 2024
Published to the GitHub Advisory Database Jul 11, 2024
Reviewed Jul 12, 2024
Last updated Sep 6, 2024

Severity

High

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-6468

GHSA ID

GHSA-2qmw-pvf7-4mw6

Source code

Credits

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