Skip to content

iOS Simulator MCP Command Injection allowed via exec API

Moderate severity GitHub Reviewed Published Jun 25, 2025 in joshuayoes/ios-simulator-mcp • Updated Jun 26, 2025

Package

npm ios-simulator-mcp (npm)

Affected versions

< 1.3.3

Patched versions

1.3.3

Description

Command Injection in MCP Server

The MCP Server at https://github.com/joshuayoes/ios-simulator-mcp/ is written in a way that is vulnerable to command injection vulnerability attacks as part of some of its MCP Server tool definition and implementation.

Vulnerable tool

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.

Vulnerable line of code: https://github.com/joshuayoes/ios-simulator-mcp/blob/main/src/index.ts#L166-L207

  server.tool(
    "ui_tap",
    "Tap on the screen in the iOS Simulator",
    {
      duration: z.string().optional().describe("Press duration"),
      udid: z
        .string()
        .optional()
        .describe("Udid of target, can also be set with the IDB_UDID env var"),
      x: z.number().describe("The x-coordinate"),
      y: z.number().describe("The x-coordinate"),
    },
    async ({ duration, udid, x, y }) => {
      try {
        const actualUdid = await getBootedDeviceId(udid);
        const durationArg = duration ? `--duration ${duration}` : "";
        const { stderr } = await execAsync(
          `idb ui tap --udid ${actualUdid} ${durationArg} ${x} ${y}  --json`
        );

Exploitation

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.

Reference example from prior security research on this topic:

Cursor defined MCP Server vulnerable to command injection

Impact

User initiated and remote command injection on a running MCP Server.

References and Prior work

  1. Exploiting MCP Servers Vulnerable to Command Injection
  2. Liran's Node.js Secure Coding: Defending Against Command Injection Vulnerabilities

Disclosed by Liran Tal

References

@joshuayoes joshuayoes published to joshuayoes/ios-simulator-mcp Jun 25, 2025
Published by the National Vulnerability Database Jun 26, 2025
Published to the GitHub Advisory Database Jun 26, 2025
Reviewed Jun 26, 2025
Last updated Jun 26, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(31st percentile)

Weaknesses

CVE ID

CVE-2025-52573

GHSA ID

GHSA-6f6r-m9pv-67jw

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.