T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:105
- Finding
- Unverified Automatic Download of a Native Dependency## Vulnerability Details **File Location**: `SKILL.md`, lines 105-112 **Vulnerability Type**: Unverified automatic retrieval of a third-party native library **Risk Level**: Medium **Vulnerable Code Snippet**: ```markdown ## Requirements - `camera_models` - C++ library (auto-downloaded via gettool if missing) - `numpy` - Array operations - `pywayne.cv.tools.write_cv_yaml` - For writing YAML files ## Notes - Library is automatically checked and downloaded via `gettool` if not found ``` ### Technical Analysis The documented workflow automatically downloads the native `camera_models` C++ library through `gettool` when the dependency is unavailable. The documentation does not specify an authoritative download URL, an immutable version, a cryptographic checksum, a digital signature, or an explicit user-approval step. Because a native library executes inside the importing process, substitution or compromise of the dependency source could result in arbitrary native code execution. The reviewed project contains only `SKILL.md`; therefore, the implementation of `gettool`, its transport protections, and any artifact-integrity verification could not be inspected. The finding is consequently based on the explicitly documented automatic-download behavior and missing documented safeguards, not on a confirmed malicious payload. ### Attack Path 1. A user follows the documented workflow and imports or initializes the camera-model wrapper. 2. The expected `camera_models` native library is not present locally. 3. The wrapper automatically invokes `gettool` to retrieve an unspecified dependency artifact. 4. An attacker compromises or controls the artifact source, resolution process, network path, or mutable upstream release. 5. Without checksum or signature verification, the substituted native library is accepted. 6. The malicious library is loaded into the Python process and executes with that process's permissions. ### Impac ...[truncated 585 chars]
- Remediation
- ## Remediation Suggestions 1. Pin `camera_models` to an exact, immutable release rather than resolving a mutable or unspecified version. 2. Restrict downloads to a documented, trusted HTTPS source under the maintainers' control. 3. Publish and verify a cryptographic checksum, such as SHA-256, before loading the downloaded artifact. 4. Prefer signed release artifacts and validate signatures against a pinned, trusted signing key. 5. Fail closed if integrity or authenticity verification fails. 6. Require explicit user consent before downloading or loading native code; preferably require dependency installation as a separate administrative step. 7. Cache artifacts only after successful verification and protect the cache against unauthorized modification. 8. Record the resolved source, version, checksum, and verification outcome for auditing and reproducible builds. 9. Document the dependency acquisition and integrity controls in `SKILL.md`. 10. Review the unavailable `gettool` implementation to confirm secure transport, strict source allowlisting, integrity validation, safe archive extraction, and resistance to dependency confusion.