openssl-encrypt before 1.4.9 Output Injection via Unsanitized Filenames in verify-usb Command
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
The openssl-encrypt Python package (before version 1.4.9) is affected, specifically its verify-usb command. An attacker who can place files on a USB drive could use specially crafted filenames to manipulate the terminal output, making it appear that tampered data passed verification.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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().
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- jahlives openssl_encrypt
fixed in 1.4.9
- openssl-encryptPyPI
fixed in 1.4.9