An unauthenticated server-side request forgery vulnerability in OpenMAIC allows attackers to access sensitive cloud instance metadata and credentials.

The vulnerability exists because the application skips server-side request forgery validation in non-production environments. An unauthenticated attacker can supply arbitrary URLs via the x-base-url header or baseUrl parameter to the /api/generate/image endpoint, forcing the server to perform requests to internal cloud resources.

Successful exploitation allows an attacker to bypass internal network boundaries and interact with cloud metadata services (such as AWS, GCP, or Azure metadata endpoints). This can result in the unauthorized retrieval of sensitive cloud instance credentials, security tokens, or infrastructure configuration data, leading to a complete compromise of the affected cloud instance or associated resources. Given the CVSS score of 7.5, this high-severity vulnerability poses a significant risk to organizational confidentiality and infrastructure integrity.

Immediate Action: Upgrade OpenMAIC to version 1.0.1 or later immediately to incorporate the necessary URL validation logic.

Proactive Monitoring: Review web server and application logs for anomalous requests to the /api/generate/image endpoint, specifically monitoring for unusual x-base-url headers or internal metadata IP addresses (e.g., 169.254.169.254).

Compensating Controls: If an immediate upgrade is not feasible, implement a Web Application Firewall (WAF) rule to block or inspect the x-base-url and baseUrl parameters for suspicious or internal-facing destination URLs.

Public Exploit Available: No

The vulnerability represents a critical security oversight in the application's request handling logic. Organizations must prioritize upgrading to version 1.0.1 to ensure that SSRF validation is enforced regardless of the deployment environment. Failing to patch this vulnerability leaves the underlying cloud infrastructure exposed to unauthorized access and credential theft.