T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Installation and Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent PDF helper, but its signing instructions can expose certificate passwords or private keys and its install command pulls an unpinned package.
Review the signing instructions before installing or using this skill. Prefer a pinned, trusted pdfly version, avoid passing certificate or PDF passwords directly in commands, do not export private keys with unencrypted OpenSSL options for verification, and keep backups or explicit output files when modifying PDFs.
SKILL.md:15Unpinned Third-Party Package Installation and Execution
references/sign.md:24PKCS12 Password Exposed Through Command-Line Arguments
references/sign.md:93Private Signing Key Exported Without Encryption
The skill recommends running uvx pdfly without pinning a specific version, which allows whatever latest package version is available at execution time to be fetched and run. That creates a supply-chain risk: a malicious or compromised upstream release could be executed through the skill, and the skill context makes this more relevant because it is explicitly providing an installation/execution command users may copy directly.
The documentation includes an in-place signing example that modifies the original PDF without an explicit warning that the operation overwrites the source file. In a CLI skill intended for file manipulation, this increases the chance of accidental irreversible data loss, especially if users run examples verbatim on important documents.
The example passes the PKCS12 password directly on the command line, which can expose the secret via shell history, process listings, audit logs, or telemetry. Because this skill handles signing certificates, credential exposure is more dangerous than in ordinary tooling: compromise of the certificate password may enable unauthorized document signing or key extraction depending on environment and key handling.
The markdown documents a signing command using a PKCS12 certificate (--p12 CERT) but does not include any warning that the operation involves sensitive credential material. For markdown files, safety-relevant behaviors affecting privacy or credentials should be disclosed so users understand the implications before use.
This markdown file documents operations that create output files and can split, merge, remove, or reorder PDF pages, which affect user data and system state. The description and options explain how to perform these actions but do not warn users about potential overwrites, data loss, or the need to choose a safe output path.
No suspicious patterns detected.