[DepShield] (CVSS 7.4) Vulnerability due to usage of lodash.uniq:4.5.0
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- build-system, security
Research direction
Start by inspecting the dependency configuration and tracing the reported path from react-scripts:5.0.0 through css-minimizer-webpack-plugin, cssnano, and postcss-colormin to lodash.uniq:4.5.0. Confirm the vulnerability is no longer present in the dependency tree and that the project still builds successfully.
Written by the indexing model from the issue text.
Description
Vulnerabilities
DepShield reports that this application's usage of lodash.uniq:4.5.0 results in the following vulnerability(s):
- (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
- (CVSS 6.5) [CVE-2018-3721] lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...
Occurrences
lodash.uniq:4.5.0 is a transitive dependency introduced by the following direct dependency(s):
• react-scripts:5.0.0
└─ css-minimizer-webpack-plugin:3.3.1
└─ cssnano:5.0.14
└─ cssnano-preset-default:5.1.9
└─ postcss-colormin:5.2.2
└─ caniuse-api:3.0.0
└─ lodash.uniq:4.5.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
- JavaScript
- 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/react-chatbot
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mog-rn/react-chatbot#8 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mog-rn/react-chatbot#7 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mog-rn/react-chatbot#6 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
mog-rn/react-chatbot#4 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
mog-rn/react-chatbot#3 ·
All issues in mog-rn/react-chatbot
Similar issues
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TanbirRamim/open-source-radar#353 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 2 days
-
design-review mac P3 ui
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tosunlab/hisarapp-core#502 ·
-
enhancement status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mastra-ai/mastra#28651 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement frontend help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
nikhilb2/simple_invoicing#470 ·
Maintainers usually reply within 1 day