VDB
Sign up
CRITICAL9.1

GHSA-hrh2-vp3x-79xf

@xhmikosr/decompress: Path traversal via symlink chain

Quick fix

GHSA-hrh2-vp3x-79xf — @xhmikosr/decompress: upgrade to the fixed version with the command below.

npm install @xhmikosr/decompress@11.1.4

Details

### Impact

When extracting an untrusted archive with the default `decompress(input, output)` API, a crafted archive containing a chain of symlink entries can make a later entry resolve **outside** the output directory. The lexical containment checks pass, but the kernel follows the planted symlinks to a path outside `output`, letting an attacker write (and read) files outside the intended extraction directory. Overwriting startup scripts or configuration can lead to remote code execution.

This is a bypass of the hardening in GHSA-mp2f-45pm-3cg9. Any application that extracts attacker-controlled archives is affected.

### Patches

Fixed in **11.1.4** (`latest`) and backported to **10.2.2** (`release-v10` dist-tag). Upgrade to one of these.

The unmaintained upstream `decompress` package shares this flaw and will not be patched. Migrate to `@xhmikosr/decompress@11.1.4` (or `@10.2.2`).

### Workarounds

None. Do not extract untrusted archives on affected versions. If you cannot upgrade, validate entries out of band and reject any whose resolved path escapes the target directory.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm/@xhmikosr/decompress
Introduced in: 11.0.0Fixed in: 11.1.4
Fixnpm install @xhmikosr/decompress@11.1.4
npm/@xhmikosr/decompress
Introduced in: 0Fixed in: 10.2.2
Fixnpm install @xhmikosr/decompress@10.2.2
npm/decompress
Introduced in: 0

No fixed version published yet for decompress (npm). Pin to a known-safe version or switch to an alternative.

References