CVE-2024-1052: Boundary Vulnerable to Session Hijacking Through TLS Certificate Tampering
Boundary and Boundary Enterprise (“Boundary”) is vulnerable to session hijacking through TLS certificate tampering. An attacker with privileges to enumerate active or pending sessions, obtain a private key pertaining to a session, and obtain a valid trust on first use (TOFU) token may craft a TLS certificate to hijack an active session and gain access to the underlying service or application.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/hashicorp/boundaryto a version that resolves this vulnerability.Fixed in 0.15.0
Event History
Frequently Asked Questions
What is the severity of CVE-2024-1052?
CVE-2024-1052 is considered a critical vulnerability due to its potential for session hijacking.
How do I fix CVE-2024-1052?
To resolve CVE-2024-1052, upgrade to Boundary version 0.15.0 or later.
What types of systems are affected by CVE-2024-1052?
CVE-2024-1052 affects systems running HashiCorp Boundary versions between 0.8.0 and 0.15.0.
What is the impact of exploiting CVE-2024-1052?
Exploiting CVE-2024-1052 allows attackers to hijack user sessions, potentially compromising sensitive data.
Who can be targeted by CVE-2024-1052?
Attackers can target any user with active or pending sessions in affected instances of HashiCorp Boundary.