Vulnerability Description
iOS Simulator MCP Server (ios-simulator-mcp) is a Model Context Protocol (MCP) server for interacting with iOS simulators. Versions prior to 1.3.3 are written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation. The MCP Server exposes the tool `ui_tap` which relies on Node.js child process API `exec` which is an unsafe and vulnerable API if concatenated with untrusted user input. LLM exposed user input for `duration`, `udid`, and `x` and `y` args can be replaced with shell meta-characters like `;` or `&&` or others to change the behavior from running the expected command `idb` to another command. When LLMs are tricked through prompt injection (and other techniques and attack vectors) to call the tool with input that uses special shell characters such as `; rm -rf /tmp;#` and other payload variations, the full command-line text will be interepted by the shell and result in other commands except of `ps` executing on the host running the MCP Server. Version 1.3.3 contains a patch for the issue.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/joshuayoes/ios-simulator-mcp/blob/main/src/index.ts#L166-L207
- https://github.com/joshuayoes/ios-simulator-mcp/commit/eb53a4f2cc8bbeb13e8d6d930
- https://github.com/joshuayoes/ios-simulator-mcp/releases/tag/v1.3.3
- https://github.com/joshuayoes/ios-simulator-mcp/security/advisories/GHSA-6f6r-m9
FAQ
What is CVE-2025-52573?
CVE-2025-52573 is a vulnerability with a CVSS score of 6.0 (MEDIUM). iOS Simulator MCP Server (ios-simulator-mcp) is a Model Context Protocol (MCP) server for interacting with iOS simulators. Versions prior to 1.3.3 are written in a way that is vulnerable to command in...
How severe is CVE-2025-52573?
CVE-2025-52573 has been rated MEDIUM with a CVSS base score of 6.0/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-52573?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.