/

CVE-2025-66687

Severity:

HIGH RISK

(7.5)

Directory Traversal / Path Traversal in Doom Launcher Game

CVE-2025-66687

Deferred

Vulnerability type

Category:

Directory Traversal / Path Traversal

CWE:

CWE-22

Impact:

Arbitrary File Write and Potential Local Compromise

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Doom Launcher 3.8.1.0 contains a directory traversal vulnerability in its game file extraction logic, where archive paths are not properly validated before being written to disk.

An attacker who can supply or influence extracted game archives may cause files to be written outside the intended game directory, potentially overwriting or planting files in arbitrary locations on the user's system.

Affected context

The issue arises when Doom Launcher 3.8.1.0 extracts game-related archives (such as WADs, PK3s, or other bundled content) to the local filesystem.

If the application trusts the file paths embedded in the archive without normalizing and constraining them to the intended target directory, an attacker-controlled or tampered archive can escape the extraction folder.

This becomes especially risky when users download game packs, mods, or map bundles from untrusted sources and import them through the launcher.

Exploit preconditions

  • Attack surface: Local application handling of user-supplied archives or game content packages.
  • Required access: Ability to get a victim to open or import a crafted archive through Doom Launcher (e.g., via download, file sharing, or bundled mod packs).
  • Trigger point: The moment Doom Launcher extracts files from the archive to the filesystem without validating or sanitizing the internal paths.
  • Why exploitation is possible: The extraction logic does not normalize or restrict file paths to a safe base directory, allowing constructs like ../ or absolute paths to direct files outside the intended game folder.

Why this happens

The root cause is improper restriction of file paths derived from untrusted archive contents, corresponding to CWE-22: Improper Limitation of a Pathname to a Restricted Directory.

Instead of enforcing that every extracted file path remains within a predefined game or data directory, the application appears to accept paths as-is and write them to disk.

This insecure pattern allows attackers to leverage relative path traversal sequences or absolute paths to escape the extraction directory and target arbitrary locations on the user's machine.

Potential impact

  • Overwriting existing files within the user's home or application directories (e.g., configuration files, scripts).
  • Planting new files in sensitive locations that could later be executed or loaded by other applications.
  • Tampering with Doom Launcher or game engine configuration to alter behavior or load malicious content.
  • Indirect escalation of impact if other software auto-runs or trusts files from the affected directories.
  • Loss of data integrity within the game environment or broader user profile.

General mitigation guidance

Effective mitigation focuses on enforcing strict path handling and limiting where files can be written during extraction:

  • Normalize all archive entry paths and reject any that resolve outside a predefined, trusted base directory.
  • Strip or reject directory traversal sequences (e.g., ../) and absolute paths from archive entries before writing to disk.
  • Use filesystem APIs that can resolve and compare canonical paths to ensure they remain rooted in the intended game content directory.
  • Run the launcher and its extraction routines with least-privilege filesystem permissions, avoiding elevated rights where possible.
  • Treat all externally sourced game content and mods as untrusted input and apply the same path validation logic consistently.

How teams detect issues like this

Detection generally involves reviewing and analyzing file handling code paths where archives are processed:

  • Use static analysis tools or custom rules to flag any extraction logic that writes files based directly on archive entry names without normalization or boundary checks.
  • During code review, look for calls that construct file paths from user-controlled or external content (e.g., concatenating archive entry names with base directories) and verify they enforce directory constraints.
  • Implement logging around file extraction operations, including the resolved destination paths, and monitor for paths that escape the expected game content directory.
  • Incorporate security-focused tests (e.g., unit or integration tests) using crafted archives containing traversal sequences to ensure the extraction logic blocks them.

Sources

SourceLink
github.comgithub.com/nstlaurent/DoomLauncher/issues/369
jeroscope.comjeroscope.com/advisories/2025/jero-2025-014/

Frequently asked

questions

Not directly over the network by itself. Exploitation typically requires convincing a user to open a crafted game archive or mod pack in Doom Launcher, but this can be facilitated via malicious downloads, mod repositories, or file sharing.

An attacker needs the ability to provide or influence the game archive that the victim imports into Doom Launcher. Once the victim processes the crafted archive, the vulnerable extraction logic can write files outside the intended directory.

The safest fix pattern is to enforce strict path normalization and validation for all archive entries, rejecting any path that resolves outside a designated, restricted game content directory, and ignoring absolute or traversal-containing paths.

Treat all file paths from external content as untrusted, centralize path canonicalization and validation routines, add automated tests for traversal cases, and include filesystem security checks as part of regular code reviews and continuous integration pipelines.

Find out what's already
exploitable in your codebase.