CVE-2024-6468
Last modified
CVE-2024-6468 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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.. EPSS estimates a 0.49% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Hashicorp | Vault | >= 1.10.0, < 1.15.12 |
| Hashicorp | Vault | >= 1.16.0, < 1.16.6 |
| Hashicorp | Vault | >= 1.17.0, < 1.17.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-6468?
How severe is CVE-2024-6468?
How do I fix CVE-2024-6468?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-6462The DL Yandex Metrika WordPress plugin through 1.2 does not …4.8
- CVE-2024-6463Rejected reason: **REJECT** This is a duplicate CVE issued i…
- CVE-2024-6464Rejected reason: **REJECT** This is a duplicate CVE issued i…
- CVE-2024-6465The WP Links Page plugin for WordPress is vulnerable to unau…4.3
- CVE-2024-6466NEC Corporation's WebSAM DeploymentManager v6.0 to v6.80 all…5.3
- CVE-2024-6467The BookingPress – Appointment Booking Calendar Plugin and O…8.8
- CVE-2024-6469A vulnerability was found in playSMS 1.4.3. It has been decl…8.8
- CVE-2024-6470A vulnerability was found in playSMS 1.4.3. It has been rate…2.7
- CVE-2024-6471A vulnerability classified as critical has been found in Sou…8.8
- CVE-2024-6472Certificate Validation user interface in LibreOffice allows …7.8
- CVE-2024-6473Yandex Browser for Desktop before 24.7.1.380 has a DLL Hijac…7.8
- CVE-2024-6474Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2024-6468?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
