T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Uncontrolled Cross-Skill Instruction Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:18
Vulnerability Type: Unversioned external Skill dependency outside the project root
Risk Level: MediumVulnerable Code Snippet:
markdown | **G3 — Verification** | Before publishing review output, you applied the **[review-verification-protocol](../review-verification-protocol/SKILL.md)** to each proposed finding. |Technical Analysis
The Skill makes successful completion of its review process dependent on instructions loaded from
../review-verification-protocol/SKILL.md. This relative path escapes the audited project root, while the referenced Skill is not bundled, version-pinned, or integrity-verified by this artifact.Consequently, the effective behavior of the Skill cannot be determined solely from the reviewed files. The dependency could be absent, causing the verification gate to fail, or replaced with different instructions after this Skill has been audited. If an attacker can create or modify the sibling path, the mandatory G3 gate causes attacker-controlled instructions to be incorporated into each review.
This is a supply-chain and instruction-integrity weakness. The audited project itself contains no malicious payload, but it delegates a required part of its behavior to an uncontrolled external component.
Attack Path
- An attacker obtains write access to the parent directory or controls installation of the sibling
review-verification-protocolSkill. - The attacker creates or modifies
../review-verification-protocol/SKILL.mdwith instructions designed to suppress findings, alter severity ratings, disclose review data, or redirect the agent's output. - A user invokes the
bubbletea-code-reviewSkill. - The G3 hard gate requires the agent to load and apply the sibling Skill before publishing findings.
- The attacker-controlled instructions influence the audit process and its final report.
Exploitation therefore requi ...[truncated 797 chars]
- An attacker obtains write access to the parent directory or controls installation of the sibling
- Remediation
View remediation
Remediation Suggestions
- Bundle the verification protocol within this project, such as under
references/, so all effective instructions are included in the auditable artifact. - Replace the parent-directory reference with a path constrained to the Skill root.
- If an external dependency is unavoidable, pin it to an immutable, trusted version and verify its cryptographic digest before use.
- Define expected behavior locally and treat external material as non-authoritative reference content rather than mandatory instructions.
- Fail closed with a clear diagnostic when the approved dependency is missing or fails integrity verification.
- Include the verification protocol in release reviews and provenance records so changes to it trigger a new security audit.
- Bundle the verification protocol within this project, such as under
