CVE-2022-36130
CVE-2022-36130 is a critical-severity vulnerability in Hashicorp Boundary with a CVSS 3.x base score of 9.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.
Key facts
- Severity: Critical (CVSS 3.x base score 9.9)
- EPSS exploit prediction: 0% (34th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-345
- Affected product: Hashicorp Boundary
- Published:
- Last modified:
Description
HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, allowing potential privilege escalation for authorized users of another scope. Fixed in Boundary 0.10.2.
Frequently asked questions
- What is CVE-2022-36130?
- HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, allowing potential privilege escalation for authorized users of another scope. Fixed in Boundary 0.10.2.
- How severe is CVE-2022-36130?
- CVE-2022-36130 has a CVSS 3.x base score of 9.9, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2022-36130 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-36130?
- CVE-2022-36130 affects Hashicorp Boundary. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2022-36130?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2022-36130 published?
- CVE-2022-36130 was published on 2022-09-01 and last updated on 2026-06-17.
References
- https://discuss.hashicorp.com
- https://discuss.hashicorp.com/t/hcsec-2022017-boundary-allowed-access-to-host-sets-and-credential-sources-for-authorized-users-of-another-scope/43493
Affected products (1)
- cpe:2.3:a:hashicorp:boundary:*:*:*:*:*:*:*:*
More vulnerabilities in Hashicorp Boundary
- CVE-2024-1052 — High (CVSS 8.0): Boundary and Boundary Enterprise (“Boundary”) is vulnerable to session hijacking through TLS certificate tampering.…
- CVE-2022-36182 — Medium (CVSS 6.1): Hashicorp Boundary v0.8.0 is vulnerable to Clickjacking which allow for the interception of login credentials,…
- CVE-2024-12289 — Medium (CVSS 5.9): Boundary Community Edition and Boundary Enterprise (“Boundary”) incorrectly handle HTTP requests during the…
- CVE-2023-0690 — Medium (CVSS 5.0): HashiCorp Boundary from 0.10.0 through 0.11.2 contain an issue where when using a PKI-based worker with a Key…
All CVEs affecting Hashicorp Boundary →
Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities
- CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
- CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
- CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
- CVE-2026-50214 — Critical (CVSS 9.8): The /v1/Plan service relies entirely on a shared global API token for full administrative management, allowing…
- CVE-2025-15385 — Critical (CVSS 9.8): Insufficient Verification of Data Authenticity vulnerability in TECNO Mobile com.Afmobi.Boomplayer allows…
- CVE-2025-8038 — Critical (CVSS 9.8): Thunderbird ignored paths when checking the validity of navigations in a frame. This vulnerability was fixed in Firefox…
Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →