[DepShield] (CVSS 8.1) Vulnerability due to usage of tar:4.4.13
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
- Domain
- build-system, security
Research direction
Start by tracing the dependency path from gulp:4.0.2 through glob-watcher, chokidar, fsevents, and node-pre-gyp to tar:4.4.13. Check the project's dependency manifest and lockfile for the resolved version, then verify that the dependency tree no longer contains the vulnerable tar release.
Written by the indexing model from the issue text.
Description
Vulnerabilities
DepShield reports that this application's usage of tar:4.4.13 results in the following vulnerability(s):
- (CVSS 8.1) [CVE-2021-32804] The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3...
- (CVSS 8.1) [CVE-2021-32803] The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3...
- (CVSS 7.5) CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- (CVSS 7.5) CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- (CVSS 7.5) CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Occurrences
tar:4.4.13 is a transitive dependency introduced by the following direct dependency(s):
• gulp:4.0.2
└─ glob-watcher:5.0.3
└─ chokidar:2.1.8
└─ fsevents:1.2.12
└─ node-pre-gyp:0.14.0
└─ tar:4.4.13
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
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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
-
area: server priority: P3 type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
appandflow/stim#4538 ·
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
transit-audio/transit#159 ·
-
enhancement triage: feasible
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
mlflow/mlflow#27201 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100