[DepShield] (CVSS 9.8) Vulnerability due to usage of decompress:4.2.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, node.js
- Domain
- build-system, security
Research direction
Start by inspecting the dependency manifest and lockfile to trace gulp-imagemin:7.1.0 through bin-build and download to decompress:4.2.0. Determine an available dependency update or replacement that removes the vulnerable version, then verify the dependency tree no longer contains decompress:4.2.0 and the DepShield findings are resolved.
Written by the indexing model from the issue text.
Description
Vulnerabilities
DepShield reports that this application's usage of decompress:4.2.0 results in the following vulnerability(s):
- (CVSS 9.8) [CVE-2020-12265] The decompress package before 4.2.1 for Node.js is vulnerable to Arbitrary File ...
- (CVSS 7.5) CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Occurrences
decompress:4.2.0 is a transitive dependency introduced by the following direct dependency(s):
• gulp-imagemin:7.1.0
└─ imagemin-gifsicle:7.0.0
└─ gifsicle:5.0.0
└─ bin-build:3.0.0
└─ decompress:4.2.0
└─ download:6.2.5
└─ decompress:4.2.0
└─ bin-wrapper:4.1.0
└─ download:7.1.0
└─ decompress:4.2.0
This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.
- Dominant language
- EJS
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mog-rn/codespace
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in mog-rn/codespace
Similar issues
-
bot-found bug priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
madenvel/KalinkaPlayer#179 ·
-
cuAmpcorParameter.cpp (CPU pycuampcor) does not compile with libc++: EXIT_FAILURE is undeclaredOpen
Difficulty 1/5 Under an hour Newbie friendliness 92/100
isce-framework/isce3#387 ·
-
agent-research-recommend agent-review-finding enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jordansmall/spindrift#3965 · 1 comment ·
Maintainers usually reply within 2 days
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
conan-io/conan-center-index#31055 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day