T08 · Insecure Dependencies
- Location
scripts/extract_exif.py:39- Finding
Runtime Installation of Unpinned Python Dependencies
- Content
View full analysis
=10.0.0", "pillow-heif"] ) from PIL import Image as PILImage from PIL.ExifTags import TAGS as PILTAGS, GPSTAGS as PILGPSTAGS from pillow_heif import register_heif_opener ``` The corresponding dependency file contains: ```text pillow>=10.0.0 pillow-heif ``` ### Technical Analysis When automatic installation is enabled, the EXIF utility invokes `pip` at runtime and retrieves mutable package releases from the configured Python package index. `pillow-heif` has no version constraint, while `pillow>=10.0.0` permits any future version satisfying the lower bound. Neither package is protected by an integrity hash. The package names are consistent with the declared image-processing feature, and there is no evidence that they are intentionally malicious. Nevertheless, installing mutable dependencies during Skill execution creates a supply-chain execution channel: package installation and import occur inside the Agent process environment without a separately reviewed lockfile or integrity check. The subprocess invocation uses an argument list rather than a shell string, so the identified issue is dependency trust rather than command injection. ### Attack Path 1. Pillow or `pillow-heif`, a transitive dependency, or the configured p ...[truncated 976 chars]- Remediation
View remediation
