# CVE-2022-36182: Hashicorp Boundary vulnerable to clickjacking

> Clickjacking in Hashicorp Boundary allows attackers to intercept credentials or force malicious actions, requiring an upgrade to mitigate.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-xqv2-3vvq-qg6r

## What is CVE-2022-36182?

CVE-2022-36182 is a medium-severity vulnerability in n/a, published on 27 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Hashicorp Boundary v0.8.0 is vulnerable to Clickjacking which allow for the interception of login credentials, re-direction of users to malicious sites, or causing users to perform malicious actions on the site.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2022-36182?

2 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 | All versions to 0.11.0 | None |
| `github.com/hashicorp/boundary` | Go | All versions to 0.11.0 | None |

Products: Hashicorp Boundary.

## How do I fix CVE-2022-36182?

No fix has been published for CVE-2022-36182 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-36182 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36130](https://insights.sbomify.com/CVE-2022-36130/): Privilege escalation in n/a (critical 9.9)
- [CVE-2024-1052](https://insights.sbomify.com/CVE-2024-1052/): Boundary Vulnerable to Session Hijacking Through TLS Certificate Tampering (high 8.0)
- [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-2022-36182 and fix it if it is affected.

What it is: CVE-2022-36182 is a medium-severity vulnerability in n/a, published on 27 Oct 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-36182 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/boundary (Go): affected all versions up to 0.11.0; no fix listed
- github.com/hashicorp/boundary (Go): affected all versions up to 0.11.0; no fix listed

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-2022-36182/ (Markdown: https://insights.sbomify.com/CVE-2022-36182/index.md)
```

## Sources

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

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