T08 · Insecure Dependencies
- Location
scripts/ios-self-improve.sh:258- Finding
Unpinned Dependency Executed Without Authenticity or Integrity Validation
- Content
View full analysis
Vulnerability Details
File Location:
scripts/ios-self-improve.sh:258-263
Related Locations:.clawhub.json:11-13,SKILL.md:27-32,README.md:9-16
Vulnerability Type: Insecure dependency execution and supply-chain trust
Risk Level: MediumVulnerable Code
bash # Call developer-self-improve-core's post-check local auto_script="$SKILL_DIR/../developer-self-improve-core/scripts/developer-self-improve-core.sh" if [ -f "$auto_script" ]; then "$auto_script" post-check "$content" "$scene" else echo "⚠️ developer-self-improve-core is not installed; unable to generate a draft" fiThe dependency is declared without a version or immutable identifier:
json "dependencies": [ "developer-self-improve-core" ]The installation instructions likewise request an unversioned package:
bash clawhub install developer-self-improve-coreTechnical Analysis
The
proposeoperation executes a shell script from a predictable sibling directory. The only runtime validation is Bash's-ftest, which establishes that the path is a regular file but does not verify:- Package version or immutable digest
- Cryptographic signature or checksum
- File ownership and permissions
- Canonical path and package identity
- Whether the sibling installation has been replaced or modified
- Whether the dependency release is the version previously audited
Consequently, the effective code executed by this Skill is not fully represented by the audited package. A compromised dependency release, package-resolution substitution, or attacker-controlled sibling directory can alter runtime behavior.
This behavior also conflicts with security documentation claiming that the Skill does not execute dependency or external code. The dependency is a separately installed component, and its script is directly invoked.
The arguments are passed using proper shell quoting, so no direct shell-command injection through
$contentor$scenewas identifie ...[truncated 1734 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
developer-self-improve-coreto an audited immutable version or content digest in package metadata and installation documentation. - Require cryptographic package-signature or checksum verification before the dependency is installed or executed.
- Resolve the dependency through a trusted package-manager API instead of assuming that a writable sibling path represents the declared package.
- Before execution, canonicalize the path and verify that it remains within the expected dependency installation directory.
- Validate file ownership and reject scripts writable by unexpected users or groups.
- Replace direct shell-script invocation with a constrained, versioned interface that exchanges validated structured data where feasible.
- Document accurately that the
proposeoperation executes dependency code and inherits that dependency's security properties. - Audit the pinned dependency together with this Skill, particularly its handling of the user-controlled
contentandscenearguments. - Correct the related inaccurate claims that all operations are read-only, that no dependency code is executed, and that file existence constitutes dependency validation.
- Pin
