Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[DepShield] (CVSS 7.4) Vulnerability due to usage of lodash.sortby:4.7.0

Open
  • Is something wrong?
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, react
Domain
build-system, frontend, security

Research direction

Start by inspecting the dependency declarations and lockfile for the react-scripts 5.0.0 dependency chain through workbox-webpack-plugin, workbox-build, source-map, and whatwg-url. Confirm how lodash.sortby 4.7.0 is resolved and verify that the completed dependency update removes the reported CWE-471 vulnerability.

Written by the indexing model from the issue text.

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):

• react-scripts:5.0.0
        └─ workbox-webpack-plugin:6.4.2
              └─ workbox-build:6.4.2
                    └─ source-map:0.8.0-beta.0
                          └─ whatwg-url:7.1.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.

Dominant language
JavaScript
Stars
0
Forks
0
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mog-rn/react-chatbot

All issues in mog-rn/react-chatbot

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.