Описание
eml_parser: Path Traversal in Official Example Script Leads to Arbitrary File Write
Summary
The official example script examples/recursively_extract_attachments.py contains a path traversal vulnerability that allows arbitrary file write outside the intended output directory. Attachment filenames extracted from parsed emails are directly used to construct output file paths without any sanitization, allowing an attacker-controlled filename to escape the target directory.
Details
File: examples/recursively_extract_attachments.py
Lines: 61–64
The value a['filename'] is attacker-controlled via crafted email attachment headers:
No path normalization or boundary validation is performed before writing.
PoC
- Create a malicious
.emlfile:
- Run the example script:
- Expected:
./safe/pwned.txt - Actual:
./outside/pwned.txt← written outside the intended directory
Verified on Kali Linux with eml_parser installed via pip in a virtual environment.
Impact
This vulnerability is limited to the example script only and does not affect the core eml_parser library. However, as the script is part of the official repository and is likely to be adapted for production use, an attacker supplying a crafted email could achieve arbitrary file write within the execution context.
Potential attack scenarios include:
- Cron job injection:
filename="../../etc/cron.d/backdoor" - Web shell upload:
filename="../../var/www/html/shell.php" - SSH key injection:
filename="../../home/user/.ssh/authorized_keys"
Recommended Fix
Пакеты
eml-parser
< 2.0.1
2.0.1
Связанные уязвимости
eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. Prior to version 2.0.1, the official example script examples/recursively_extract_attachments.py contains a path traversal vulnerability that allows arbitrary file write outside the intended output directory. Attachment filenames extracted from parsed emails are directly used to construct output file paths without any sanitization, allowing an attacker-controlled filename to escape the target directory. This issue has been patched in version 2.0.1.