AWS API MCP Server Security Policy Bypass via Startup Failure
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.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Aws | Aws-api-mcp-server |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-29w2-fq35-v728 | AWS API MCP Server Security Policy Bypass via Startup Initialization Failure |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.227% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper handling of an initialization failure in AWS API MCP Server from 0.2.13 through 1.3.46 might allow an actor to bypass the user-configured security policy and execute AWS API operations that the policy was set to deny or gate. When initialization of the security policy enforcement data fails at server startup, the policy check is skipped for the lifetime of the process. IAM permissions on the configured credentials remain in effect and are unaffected. To remediate this issue, users should upgrade to version 1.3.47. | |
| Title | AWS API MCP Server Security Policy Bypass via Startup Failure | |
| First Time appeared |
Aws
Aws aws-api-mcp-server |
|
| Weaknesses | CWE-455 | |
| CPEs | cpe:2.3:a:aws:aws-api-mcp-server:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Aws
Aws aws-api-mcp-server |
|
| References |
| |
| Metrics |
cvssV3_1
|