Decompress npm Package Vulnerability Under Investigation
An early warning has been issued regarding a potential vulnerability in the @xhmikosr/decompress npm package, which may allow the creation of files and links outside the target directory during archive extraction. This issue is under investigation and affects versions prior to 11.1.3.
What happened
The @xhmikosr/decompress npm package, used for extracting archives, is reportedly vulnerable to creating files and links outside the intended target directory. This issue affects all archive formats handled by the package, including tar, tar.gz, tar.bz2, and zip. The vulnerability is tracked under GHSA-MP2F-45PM-3CG9 and has been addressed in version 11.1.3.
Professional software engineers using this package in their projects should assess their exposure by checking the version of @xhmikosr/decompress in use. Any version prior to 11.1.3 is potentially affected. It is recommended to upgrade to version 11.1.3 or later to mitigate the risk.
For more detailed information, primary sources should be consulted. The GitHub Advisory Database provides further insights into the vulnerability and the fix. As this is an early warning and the situation is under investigation, it is crucial to stay updated with the latest information from reliable sources.
How 0Day mitigates this
@xhmikosr/decompress is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.