Jahlives openssl_encrypt
openssl-encrypt before 1.4.9 Output Injection via Unsanitized Filenames in verify-usb Command
openssl-encrypt (pip package, versions <= 1.4.8) fails to sanitize filenames read from untrusted drive data (outside the AES-GCM authenticated manifest) before printing them in the verify-usb command's output. An attacker can plant filenames containing terminal cursor-movement and erase-line control bytes that repaint a forged PASSED verdict on screen, masking actual tamper detection. Fixed in 1.4.9 by routing drive-derived names through sanitize_for_display().
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.3critical · scored by CNA · CWE-117
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
jahlives openssl_encrypt
- < 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.