Summary
A path traversal vulnerability in IzPack allows malicious installer entries to place files outside the intended installation directory. When a victim runs a crafted installer, files may be written to startup folders, executable search paths, or other locations accessible to the installer's privileges.
Affected context
The vulnerability occurs in IzPack installers that process attacker-controlled PackFile target paths through the unpacking workflow. It becomes risky when path translation changes separators without normalizing parent-directory segments or verifying that the resulting destination remains within the intended installation directory.
Exploit preconditions
- Attack surface: The IzPack installer unpacking process
- Required access: Ability to supply or distribute a malicious installer package
- Trigger point: Extraction of a PackFile entry during installation
- Why exploitation is possible: The destination path may contain parent-directory traversal segments, and the resulting file path is not reliably constrained to the installation directory
Why this happens
The underlying issue is inadequate path canonicalization and destination containment enforcement. Converting path separators alone does not remove or resolve parent-directory segments, allowing a relative path to escape its intended extraction root. This behavior maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.
Potential impact
- Files may be written outside the intended installation directory
- Startup locations or executable search paths may be modified
- Existing files accessible to the installer user may be overwritten
- Malicious files may execute later through application or operating-system startup behavior
- The confidentiality, integrity, or availability of user-accessible data could be affected
General mitigation guidance
Mitigation generally focuses on treating archive entry names as untrusted and enforcing extraction-root containment.
Common defensive patterns include:
- Normalize and canonicalize candidate paths before creating files
- Verify that every resolved destination remains beneath the intended installation directory
- Reject absolute paths, parent-directory traversal, ambiguous encodings, and platform-specific path variants
- Use secure archive-extraction APIs that provide destination containment by default
- Apply least-privilege permissions to installer processes and installation targets
- Avoid allowing installers to write to sensitive startup or executable locations unless explicitly required
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis rules for archive extraction followed by filesystem writes
- Code review checks for separator conversion without canonicalization
- Searches for file construction from archive or package entry names
- Tests containing normalized, absolute, encoded, and platform-specific traversal variants
- Policy enforcement requiring destination containment checks before file creation
- Automated security review tools that flag untrusted paths reaching filesystem APIs

