T09 · Insecure Skill Coding Practices
- Location
index.js:30- Finding
Recursive Directory Hashing Follows Symbolic Links Outside the Requested Root
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This checksum skill is mostly a normal local utility, but its docs overstate verification support and its recursive directory mode can read outside the selected folder through symlinks.
Review before installing. Use it for generating local hashes only, not for automated integrity verification, because checksum-file verification is not implemented. Avoid running recursive mode on untrusted directories or directories that may contain symlinks, and prefer sha256 or sha512 over the default md5 for security-sensitive integrity checks.
index.js:30Recursive Directory Hashing Follows Symbolic Links Outside the Requested Root
The skill’s manifest and documentation overstate security-relevant capabilities by claiming checksum verification support while the feature is only planned, and they inconsistently describe supported algorithms. In a security utility, this can mislead users into trusting integrity-validation workflows that are not actually implemented, causing false assurance and potential acceptance of tampered files.
The manifest describes a utility for generating and verifying checksums from a file, but the code only computes hashes for a file or directory and prints them. The only reference to verification is a '--verify' argument marked as a placeholder, with no verification logic implemented anywhere.
The documentation presents the skill as suitable for verifying downloads and file integrity, but also states verification is only planned. For a checksum tool, this discrepancy can cause operators or downstream agents to assume integrity checks exist when they do not, leading to skipped validation and unsafe trust decisions.
The SKILL.md documentation contradicts itself about supported algorithms. The features section claims support for sha512, but the command usage sections only advertise md5, sha1, and sha256, creating ambiguity about actual behavior and intended scope.
The manifest explicitly states support for MD5, SHA1, and SHA256 only, while the code's allowed algorithm list includes 'sha512'. This is a direct description-behavior mismatch because the implementation exposes broader capability than the manifest advertises.