AWS API MCP Server Security Policy Bypass via Incorrect Operation Name Normalization
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| AWS | aws-api-mcp-server | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.374% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Incorrect normalization of operation names in the custom security policy enforcement in awslabs aws-api-mcp-server before 1.5.1 might allow an actor to execute AWS API operations across AWS services that the operator's security policy was configured to deny or require elicitation for, via calls to operations whose names contain consecutive capital letters. To remediate this issue, users should upgrade to version 1.5.1. | |
| Title | AWS API MCP Server Security Policy Bypass via Incorrect Operation Name Normalization | |
| First Time appeared |
Aws
Aws aws-api-mcp-server |
|
| Weaknesses | CWE-1025 CWE-863 |
|
| CPEs | cpe:2.3:a:aws:aws-api-mcp-server:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws aws-api-mcp-server |
|
| References |
| |
| Metrics |
cvssV3_1
|