T08 · Insecure Dependencies
- Location
SKILL.md:134- Finding
Unverifiable Privileged Executable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 134-145, 246-254, and 317
Vulnerability Type: Unverified external executable resolved from the host environment
Risk Level: HighVulnerable Code
bash # Batch-query all cluster statuses and export them as CSV atlas-pro batch \ --operation listClusters \ --groups "group1,group2,group3" \ --output cluster-health-$(date +%Y%m%d).csv \ --format csv \ --parallel 5 # ... # Batch-check backup status atlas-pro batch \ --operation listSnapshots \ --groups "group1,group2,group3" \ --output backup-status.csv \ --filter "createdAt > now-24h"bash atlas-pro batch \ --operation listClusters \ --profile all \ --output daily-report.csv \ --format csvbash atlas-pro alert start --config alert-rules.ymlThe dependency table declares:
text | atlas-pro.mjs | Script | Required | Distributed with this Skill |Technical Analysis
The Skill delegates all substantive MongoDB Atlas operations to an
atlas-proexecutable. However, the audited package contains onlySKILL.md; the declaredatlas-pro.mjsscript is not present. Its implementation, provenance, integrity, and security properties therefore cannot be reviewed.Because the examples invoke
atlas-proby a bare command name rather than a verified package-relative path, the shell resolves the executable through the host'sPATH. This creates a supply-chain and command-resolution trust boundary: an unintended, compromised, or attacker-supplied executable namedatlas-procould be selected.The executable is expected to process Atlas credentials and perform multi-project administrative operations, workflow orchestration, infrastructure changes, and automated alert responses. Consequently, executing an unverified implementation is materially more dangerous than invoking an ordinary local utility.
No evidence sho ...[truncated 1711 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the declared
atlas-pro.mjsimplementation in the Skill package so its behavior can be audited. - Invoke the implementation through a package-relative absolute path rather than relying on
PATHresolution. - If distribution as a separate dependency is intentional, identify an authenticated official source and pin an exact version and cryptographic checksum.
- Verify the dependency's signature or checksum before first use and after updates. Fail closed if verification fails.
- Do not automatically install or execute an arbitrary binary merely because it is named
atlas-pro. - Use separate Atlas credentials for production and staging, granting only the API roles required for each operation.
- Avoid
--profile allby default. Require explicit user confirmation before cross-project, destructive, or infrastructure-changing operations. - Run the executable in a restricted environment with only the necessary environment variables, filesystem access, and network destinations.
- Protect
~/.atlas-prowith directory mode0700and credential configuration files with mode0600. - Add provenance, version, and integrity-verification instructions to
SKILL.md, and document the exact administrative permissions required for every operation.
- Include the declared
