CRITICAL CVSS 9.9
Published: 2022-09-01

CVE-2022-36130

hashicorp boundary Security Advisory (CVE-2022-36130)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2022-36130?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2022-36130 impacting hashicorp boundary. Evaluated with CVSS Base Score of 9.9 (CRITICAL).

Original NVD Description

Source: NIST NVD
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.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product hashicorp / boundary
Affected Versions *
Weakness Enumeration CWE-345

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2022-36130 impacting hashicorp boundary.

⚡ Nuclei Detection Template (YAML) cve-2022-36130.yaml
id: cve-2022-36130

info:
  name: hashicorp boundary - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: critical
  description: |
    Automated signature & scanner for CVE-2022-36130 affecting hashicorp boundary.
    Evaluation: HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, allowi...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2022-36130
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 9.9
    cve-id: CVE-2022-36130
    cwe-id: CWE-345
  tags: cve,cve-2022-36130,hashicorp,boundary,critical

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "boundary"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2022-36130.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2022-36130
# Target: hashicorp boundary | CVSS: 9.9 (CRITICAL)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2022-36130 (hashicorp boundary)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against hashicorp boundary scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2022-36130.sh
# Recommended Remediation & Patching Commands for CVE-2022-36130
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install boundary 2>/dev/null || \
sudo dnf upgrade boundary 2>/dev/null || \
sudo yum update boundary

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i boundary 2>/dev/null || rpm -qa | grep -i boundary

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2022-36130 in hashicorp boundary?

Review vendor-specific security notices and update hashicorp boundary packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2022-36130?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2022-36130?

CVE-2022-36130 is classified with a CVSS 3.1 Base Score of 9.9 (CRITICAL). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
9.9
CRITICAL SEVERITY
CVE ID CVE-2022-36130
Weakness CWE-345
Vendor hashicorp
Product boundary
Published 2022-09-01
Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H