mog-rn / mog-rn/wasify-backendAPI
[DepShield] (CVSS 7.4) Vulnerability due to usage of lodash.sortby:4.7.0
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Vulnerabilities
DepShield reports that this application's usage of lodash.sortby:4.7.0 results in the following vulnerability(s):
Occurrences
lodash.sortby:4.7.0 is a transitive dependency introduced by the following direct dependency(s):
• jest:26.6.0
└─ @jest/core:26.6.0
└─ jest-config:26.6.0
└─ jest-environment-jsdom:26.6.0
└─ jsdom:16.4.0
└─ whatwg-url:8.4.0
└─ lodash.sortby:4.7.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.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Inspect the dependency manifest and lockfile to trace the Jest 26.6.0 dependency chain that introduces lodash.sortby 4.7.0. Determine an available dependency update or remediation, then run the Jest test suite and verify that the vulnerable transitive dependency is no longer present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100