Host command execution via crafted MCP prompt
Published May 28, 2025 · Updated May 28, 2025
Command injection in Alexei Ledenev AWS MCP Server before 1.3.0 allows remote attackers to execute arbitrary host commands via a crafted prompt. The CLI executor passes model-supplied AWS CLI text, including shell metacharacters and pipelines, to a shell without effective validation. Execution occurs when an MCP client accesses the malicious prompt; commands inherit the server process's host access and configured AWS credentials.
Summary
What happened
Command injection in Alexei Ledenev AWS MCP Server before 1.3.0 allows remote attackers to execute arbitrary host commands via a crafted prompt. The CLI executor passes model-supplied AWS CLI text, including shell metacharacters and pipelines, to a shell without effective validation. Execution occurs when an MCP client accesses the malicious prompt; commands inherit the server process's host access and configured AWS credentials.
The record
- CVE
- CVE-2025-5277
- Published
- May 28, 2025
- Updated
- May 28, 2025
- Vendor
- Alexei Ledenev
- Product
- AWS MCP Server
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2025CVE publishedPublication date reported by the CVE source.
- May 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.3.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo