T07 · Tool Hijacking and Spoofing
- Location
SKILL.md:31- Finding
Unbundled Core Executable Is Invoked Through PATH Resolution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:31-42, corroborated byREADME.md:132-137andscripts/start.js:14-21
Vulnerability Type: Untrusted executable resolution through the system PATH
Risk Level: HighVulnerable Code
SKILL.md:31-42directs the agent to invoke the executable by its bare command name:text | User instruction | Main-session behavior | |------------------|-----------------------| | `Start [task description]` | Run `milestone-executor start "task" "m1|m2|m3"` | | `Continue` | Run `milestone-executor continue <workSessionKey>` | | `Stop` | Run `milestone-executor stop <workSessionKey>` | | `Report` | Run `milestone-executor status` | | `retry` | Run `milestone-executor retry <workSessionKey>` | | `skip` | Run `milestone-executor skip <workSessionKey>` | | `rollback` | Run `milestone-executor rollback` | | `Modify [content]` | Run `milestone-executor modify <workSessionKey> "content"` | | `Recover` | Run `milestone-executor recover` |README.md:132-137represents the executable as part of the package, but it is absent from the audited directory:text milestone-execution/ ├── SKILL.md # Skill definition ├── README.md # This file └── scripts/ ├── milestone-executor # Core execution script ├── start.js # Deprecated launcher └── state.js # Deprecated state managerscripts/start.js:14-21also redirects users to the missing executable:javascript console.log(` ⚠️ start.js is deprecated Please use milestone-executor: milestone-executor start "task description" "m1|m2|m3" Or use the full path: ~/.openclaw/skills/milestone-execution/scripts/milestone-executor start "task" "m1|m2|m3" `);Technical Analysis
The documented core executable,
milestone-executor, is not present in the audited package ...[truncated 2532 chars]- Remediation
View remediation
Remediation Suggestions
- Bundle the reviewed
milestone-executorimplementation inside the package at the location declared by the documentation. - Invoke it through a canonical package-relative or resolved absolute path rather than through PATH lookup, for example by resolving the path from the skill installation directory.
- Before execution, verify that the target exists, is a regular file, has expected ownership and permissions, and is not a symbolic link to an untrusted location.
- Add an integrity check using a trusted manifest or cryptographic digest distributed with the package.
- Fail closed if the bundled executable is missing or fails verification. Do not fall back to an executable found elsewhere in
PATH. - Remove or update documentation that lists files not included in the artifact.
- Use a restricted execution environment with a minimal trusted PATH and least-privilege filesystem, credential, network, and session permissions.
- Add package tests that verify all documented executable paths exist and resolve within the installed package.
- Bundle the reviewed
