@digidropp/mcp

npm @digidropp/mcp

This MCP server lets AI coding agents upload Android APK and iOS IPA build files to a Digidropp account and retrieve test installation links. The main risk is that a prompt injection could cause the agent to upload any .apk or .ipa file on the computer (or a symlink with those extensions) to the user's Digidropp account.

What it can reach

Files

Reads any local file ending in .apk or .ipa (including symlinks) passed to upload_build.

Network

Sends HTTPS requests and uploads build files to the configured DIGIDROPP_API_URL.

Secrets

Reads DIGIDROPP_TOKEN and DIGIDROPP_API_URL from environment variables and sends the token as a Bearer header.

Findings

1. LowUnrestricted file path and symlink resolution in build upload

   index.js:81

   The upload_build tool resolves any path on the filesystem and checks only that the provided path string ends in .apk or .ipa before reading it with fs.openAsBlob. A prompt injection could upload .apk or .ipa files from outside the current project workspace, or upload sensitive files if a symlink ending in .apk or .ipa exists in the workspace.

   Fix: Resolve the real path with fs.realpathSync, verify that the resolved real path is inside the intended working directory, and check the file extension on the real path.