decompress: Archive extraction can create files and links outside the target directory
XhmikosR decompress
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @xhmikosr/decompress npm |
|
|
| decompress npm |
| No fix yet |
XhmikosR decompress
| Product | Affected | Fixed in |
|---|---|---|
| @xhmikosr/decompress npm |
|
|
| decompress npm |
| No fix yet |
The decompress package for Node.js extracts archives. Prior to 10.2.1 and 11.1.3, archive extraction can create files and links outside the target directory. When extracting an archive to a directory, a crafted archive can read or write files outside that directory because hardlink and symlink entries are created without checking where targets point, path containment used a string prefix comparison, and file modes failed to remove setuid, setgid, or sticky bits. This issue is fixed in @xhmikosr/decompress versions 10.2.1 and 11.1.3.
From the CVE record · GitHub_M
Archive extraction can create files and links outside the target directory. An attacker who supplies a crafted archive can cause reads or writes outside that directory when the archive is extracted; authentication requirements are not specified.
Check applications using npm @xhmikosr/decompress versions below 10.2.1 or from 11.0.0 to below 11.1.3, or npm decompress versions up to 4.2.1.