GHSA-wx3r-v6h7-frjp internetarchive Vulnerable to Directory Traversal in File.download()

• PyPI internetarchive: < 5.5.1 → fixed in 5.5.1

Impact What kind of vulnerability is it? This is a Critical severity directory traversal (path traversal) vulnerability in the `File.download()` method of the `internetarchive` library. Who is impacted? All users of the `internetarchive` library versions `< 5.5.1` are impacted. The vulnerability is particularly critical for users on Windows systems, but all operating systems are affected. Description of the vulnerability: The vulnerability existed because the `file.download()` method did not properly sanitize user-supplied filenames or validate the final download path. A maliciously crafted filename could contain path traversal sequences (e.g., `../../../../windows/system32/file.txt`) or illegal characters that, when processed, would cause the file to be written outside of the intended target directory. Potential Impact: An attacker could potentially overwrite critical system files or application configuration files, leading to a denial of service, privilege escalation, or remote code execution, depending on the context in which the library is used. Patches Has the problem been patched? Yes, the problem has been patched. What versions should users upgrade to? Users must upgrade to version 5.5.1 or later. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? There is no direct workaround that does not involve upgrading the library. The vulnerability is in the core logic of the file download process. The only alternative for users who absolutely cannot upgrade is to implement their own custom download function that: 1. Manually sanitizes all filenames using a robust method. 2. Validates that the resolved absolute path of the download target is within the intended directory before writing any files. However, this essentially re-implements the fix and is not recommended. Upgrading to the patched version is the only safe and supported solution. References • Release Notes for v5.5.1 • Commit with the fix • CVE Identifier: CVE-2025-58438