Jahlives openssl_encrypt
verify-usb before 1.4.9 Symlink Directory Traversal Code Execution
openssl-encrypt (pip package) before 1.4.9 contains a symlink-following flaw in its verify-usb v2 added-file allowlist scan. The scan enumerated the drive with rglob(), which in CPython does not descend into symlinked directories and treats the symlink as an ordinary directory, while O_NOFOLLOW on the hash side binds only the final path component. An evil-maid attacker with physical access to the removable drive could replace a tool-tree directory with a symlink to a copy containing byte-identical files plus a planted __pycache__/*.pyc file (which CPython loads in preference to recompiling the clean .py). The planted file is never enumerated, added_files stays 0, and verify-usb reports PASSED, resulting in code execution when the victim runs the portable install. Fixed in 1.4.9 (affects both 1.4.x and 1.5.x lines).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.4.9
Fixed in 1.4.9
Mitigation
Upgrade openssl_encrypt to 1.4.9 or later.
References
- Vendor advisory github.com/jahlives/openssl_encrypt/security/a…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.