Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 4 September 2020.
- Which products and versions are affected?
- bin-links (npm) < 1.1.5.
- Is there a fix for This vulnerability?
- A patch was published on 2020-08-31: Fix released in version 1.1.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked with local access, in a software library.
- Am I affected?
- Check whether you run bin-links (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Versions of bin-links prior to 1.1.5 are vulnerable to an arbitrary symlink creation flaw. The vulnerability exists in the processing of the 'bin' field within a package's configuration, which fails to properly validate that the target of a symbolic link remains within the expected node_modules directory. A local attacker or a malicious package could exploit this to create symlinks pointing to sensitive files elsewhere on the file system. This issue is resolved in version 1.1.5.
Affected products
- npm bin-links < 1.1.5
Timeline
- 2020-08-31: patched: Fix released in version 1.1.5
- 2020-09-04: disclosed: Advisory published via GitHub Advisory Database