T08 · Insecure Dependencies
Warning
- Location
SKILL.md:83- Finding
Mutable Third-Party JavaScript Loaded Without Integrity Verification
- Content
View full analysis
``` ### Technical Analysis The Skill instructs the Agent to generate HTML pages that execute JavaScript obtained from public CDNs at runtime. The Tailwind resource has no version pin, while the React dependency is constrained only to major version 18 rather than an exact immutable release. Neither script includes a Subresource Integrity (`integrity`) hash. As a result, the effective JavaScript payload can change after the Skill has been reviewed. A CDN compromise, upstream package compromise, account takeover, or unexpected mutable-version resolution could cause generated pages to execute modified JavaScript. This is classified as `T08: Insecure Dependencies` because generated artifacts rely on mutable third-party supply-chain components loaded from external sources without integrity validation. ### Attack Path 1. An Agent follows `SKILL.md` and generates a page containing the documented external script elements. 2. The generated page is opened locally or deployed through a static web server. 3. The browser requests the JavaScript resources from `cdn.tailwindcss.com` and `unpkg.com`. 4. An attacker compromises an upstream package, CDN distribution path, or mutable dependency alias. 5. The browser accepts and executes the modified response because no integrity hash validates its contents. 6. The malicious script operates with the JavaScript privileges of the generated page's origin. ### Impact Assessment Successful exploitation permits arbitrary JavaScript execution in the generated page. Depending on how the page is deployed and used, the malicious dependency could: - Read or modify page content and ap ...[truncated 545 chars]- Remediation
View remediation
``` 5. Deploy a restrictive Content Security Policy that limits `script-src` to explicitly approved origins and avoids `unsafe-inline` and `unsafe-eval` where feasible. 6. Record approved versions and hashes in the Skill so dependency changes require an explicit review. 7. Periodically scan pinned dependencies for known vulnerabilities and update them through a controlled review process. ]]>