# CVE-2024-1052: Boundary Vulnerable to Session Hijacking Through TLS Certificate Tampering

> Attackers with specific privileges can hijack active sessions by tampering with TLS certificates, gaining unauthorized access to underlying services.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-vh73-q3rw-qx7w, GO-2024-2532

## What is CVE-2024-1052?

CVE-2024-1052 is a high-severity authentication bypass vulnerability in HashiCorp Boundary, published on 5 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-1052?

3 open source packages ship an affected version, including github.com/hashicorp/boundary. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/boundary` | Go | From 0.8.0 | 0.15.0 |
| `github.com/hashicorp/boundary` | Go | From 0.8.0 | 0.15.0 |
| `github.com/hashicorp/boundary` | Go | From 0.8.0 | 0.15.0 |

Products: Hashicorp Boundary.

## How do I fix CVE-2024-1052?

Upgrade github.com/hashicorp/boundary to 0.15.0 or later.

## Is CVE-2024-1052 being exploited?

There is no known exploitation of CVE-2024-1052 in the wild and no public exploit code.

## Other vulnerabilities in HashiCorp Boundary

- [CVE-2022-36130](https://insights.sbomify.com/CVE-2022-36130/): Privilege escalation in n/a (critical 9.9)
- [CVE-2022-36182](https://insights.sbomify.com/CVE-2022-36182/): Hashicorp Boundary vulnerable to clickjacking (medium 6.1)
- [CVE-2024-12289](https://insights.sbomify.com/CVE-2024-12289/): Boundary Controller Incorrectly Handles HTTP Requests On Initialization Which May Lead to a Denial of Service (medium 5.9)
- [CVE-2023-0690](https://insights.sbomify.com/CVE-2023-0690/): Boundary Workers Store Rotated Credentials in Plaintext Even When a Key Management Service Configured (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1052 and fix it if it is affected.

What it is: CVE-2024-1052 is a high-severity authentication bypass vulnerability in HashiCorp Boundary, published on 5 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-1052 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/boundary (Go): affected from 0.8.0; fixed in 0.15.0
- github.com/hashicorp/boundary (Go): affected from 0.8.0; fixed in 0.15.0
- github.com/hashicorp/boundary (Go): affected from 0.8.0; fixed in 0.15.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1052/ (Markdown: https://insights.sbomify.com/CVE-2024-1052/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1052
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1052
- OSV: https://osv.dev/vulnerability/CVE-2024-1052

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1052/
Summaries are generated and may contain mistakes; the official description above is the record.