T08 · Insecure Dependencies
- Location
SKILL.md:23- Finding
Unverifiable External Capability Executor Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 23-44
Vulnerability Type: Untrusted and unpinned external executable dependency
Risk Level: MediumVulnerable Code
markdown ## Implementation Calls `memento_flashcards_capability()` from `capability_executor.py` ## Usage ```python from capability_executor import execute_capability execute_capability("add flashcard")Dependencies
- capability_executor.py in D:\coze-local\db
- capability_executor.py (registration + dispatch)
Linkage
- Reports failures to skill_evolver (MetaClaw) and seal_coevolution (SEAL)
- Confidence tracked via capability_executor
text ### Technical Analysis The Skill delegates its core behavior to `capability_executor.py`, but that module is not included in the audited project. The documented Python example imports it through the generic module name `capability_executor`, without a package-relative path, pinned version, integrity hash, signature, or other source-verification mechanism. Python resolves such imports through its module search path. If an attacker can place a different `capability_executor.py` in the working directory or another earlier search-path location, the attacker's module can be imported instead of the intended implementation. Because top-level Python module code runs during import, code execution may occur even before `execute_capability()` is called. The external implementation is also documented as reporting failures and tracking confidence through other systems. Since neither the executor nor those integrations are included, their network destinations, transmitted data, authorization model, and side effects cannot be verified. This is a supply-chain and dependency-trust weakness; the available evidence does not establish that the missing implementation is itself malicious. ### Attack Path 1. An attacker obtains write access to the Skill's working directory, a user-controlled ...[truncated 1409 chars]- Remediation
View remediation
Remediation Suggestions
- Include the reviewed
capability_executor.pyimplementation within the Skill package so its behavior can be audited and distributed atomically. - Place the implementation in a uniquely named package and use an explicit package-relative import rather than a generic top-level import.
- If the dependency must remain external, distribute it through a trusted registry and pin its exact version and cryptographic hash.
- Verify dependency signatures or hashes before loading the module, and fail closed when verification fails.
- Remove the machine-specific
D:\coze-local\dbdependency path and avoid adding writable or user-controlled directories toPYTHONPATHorsys.path. - Run the capability with least privilege and restrict its filesystem, credential, and network access to what flashcard management requires.
- Document all telemetry destinations, transmitted fields, retention rules, and consent controls for MetaClaw, SEAL, and confidence tracking.
- Add tests confirming that module resolution selects only the approved implementation and that the capability cannot access unrelated files or transmit unauthorized data.
- Include the reviewed
