Unauthenticated MCP Server Exposed AWS Credentials Through SSRF and File Inclusion

· Original article ↗

Summary

CloudSEK says an unauthenticated MCP server exposed a customer’s internal tools, allowing an audio proxy to access AWS metadata and read local files, exposing IAM credentials and database secrets.

Key points

  • CloudSEK reported finding a publicly reachable MCP server in an anonymized customer environment that required no authentication.
  • The server exposed internal tools, including an audio proxy that accepted arbitrary URLs without validation.
  • The proxy enabled SSRF to the AWS Instance Metadata Service, returning live IAM credentials.
  • Accepting file:// URLs also allowed local file reads, including environment variables containing plaintext database credentials.
  • The exposed tools and credentials created risks including cloud-resource access, database compromise, customer-data exposure, and abuse of telephony services.
  • CloudSEK recommends securing all MCP endpoints, restricting proxy destinations and URL schemes, requiring IMDSv2, and rotating exposed credentials.

Article Details

Victim Organization
Not disclosed
Victim Domain
Not disclosed
Incident Type
Unauthenticated MCP server exposure exploited through SSRF to AWS IMDS and local file inclusion, exposing live AWS IAM credentials and database credentials.
Data Types Exposed
  • AWS IAM credentials
  • Database credentials
  • Phone numbers
  • Call records
  • Message metadata
Affected Records
Unknown
Affected Data Size
Unknown
Operational Impact
The source reports successful retrieval of live AWS IAM credentials and plaintext database credentials, and exposure of customer phone numbers, call records, and message metadata. Broader AWS compromise, database access, remote code execution, and abuse of telephony tools are described as potential impacts, not confirmed outcomes.
Ransom Or Extortion
None reported
Claim Status
confirmed

CVE

Threat Actors

Malware

Vendors

Products

Tools

Countries

Industries

Related Articles