T08 · Insecure Dependencies
- Location
references/commercial-production-standards.md:46- Finding
Generated Applications Execute Unverified Third-Party CDN Code
- Content
View full analysis
``` Other templates similarly load document-generation libraries directly from public CDNs: ```html ``` ### Technical Analysis The Skill instructs generated courseware, games, assessments, and lesson-building applications to load executable JavaScript from public CDN domains. Although dependency versions are pinned, the templates do not use Subresource Integrity hashes. Version pinning does not prove that the response received by a browser is the reviewed artifact. If a CDN account, upstream package, DNS route, or delivery infrastructure is compromised, the remote response can execute arbitrary JavaScript in every generated application that references it. The multi-CDN fallback improves availability but expands the supply-chain trust boundary. The ...[truncated 1476 chars]- Remediation
View remediation
``` 3. Do not use an unverified secondary CDN as an automatic fallback. Maintain a reviewed local fallback with a recorded SHA-256 or SHA-384 hash. 4. Add a restrictive Content Security Policy that limits script sources, outbound connections, framing, and plugin content. 5. Maintain a dependency inventory containing exact versions, hashes, licenses, source locations, and review dates. 6. Introduce a controlled dependency-update process with vulnerability scanning and manual artifact verification. 7. Ensure generated applications fail closed with a clear error if dependency integrity verification fails. ]]>
