AWS API MCP Server OAuth Token Audience Validation Bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.6.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The AWS API MCP Server, when configured to use OAuth authentication, fails to verify that access tokens were issued for it, so a local user holding a token issued to a different application from the same identity provider could run AWS operations using the server's configured AWS credentials.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Missing token audience validation in the OAuth authentication mode of AWS API MCP Server before version 1.6.0 might allow local users to run AWS operations with the server's configured AWS credentials via an access token issued to another application by the same identity provider. To remediate this issue, users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AWS aws-api-mcp-server
From 1.3.0 · fixed in 1.6.0