DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

GHSA-JGH3-FGGC-MCPM: GHSA-jgh3-fggc-mcpm: Non-Blind Server-Side Request Forgery (SSRF) in Obot Platform

#security #cve #cybersecurity #ghsa

GHSA-jgh3-fggc-mcpm: Non-Blind Server-Side Request Forgery (SSRF) in Obot Platform

Vulnerability ID: GHSA-JGH3-FGGC-MCPM
CVSS Score: 7.6
Published: 2026-09-18

An authenticated Server-Side Request Forgery (SSRF) vulnerability in the Obot Platform allows administrative or power users to bypass IP verification and scan or query internal resources, private networks, and cloud instance metadata services (IMDS). Because response bodies and error details are reflected back to the client interface, this constitutes a non-blind SSRF.

TL;DR

A non-blind SSRF in Obot Platform < 0.23.0 allows privileged users to query local network assets and extract cloud metadata credentials (such as AWS IAM tokens) via remote MCP registration.

⚠️ Exploit Status: POC

Technical Details

  • CWE ID: CWE-918, CWE-1188
  • Attack Vector: Network (AV:N)
  • CVSS Score: 7.6 (High)
  • Impact: Confidentiality High, Integrity Low, Availability None
  • Exploit Status: Proof-of-Concept / Conceptual
  • KEV Status: Not Listed

Affected Systems

  • Obot Platform
  • Obot Platform: < 0.23.0 (Fixed in: 0.23.0)

Code Analysis

Commit: 0d959d9

Fix outbound SSRF in remote MCP setup and OAuth discovery metadata fetches by enforcing loopback, private IP, and link-local address validation.

Mitigation Strategies

  • Upgrade Obot Platform to version 0.23.0 or later to enable default IP blocklists.
  • Implement dial-time socket verification to prevent DNS Rebinding.
  • Deploy Kubernetes NetworkPolicies to block egress access to 169.254.169.254 and RFC 1918 networks.
  • Enable IMDSv2 with a hop limit of 1 on cloud instances to mitigate SSRF attempts against metadata endpoints.

Remediation Steps:

  1. Assess current deployment versions to identify if any run on <= 0.22.1 with authentication active.
  2. Modify deployment configuration or Helm chart values to reference tag v0.23.0 or higher.
  3. Verify that variables OBOT_SERVER_DISALLOW_LOCALHOST_MCP, OBOT_SERVER_DISALLOW_PRIVATE_IP_MCP, and OBOT_SERVER_DISALLOW_LINK_LOCAL_MCP are set to true.
  4. Check application logs for resolution-blocking errors to identify potential scanning attempts.

References

Read the full report for GHSA-JGH3-FGGC-MCPM on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)