Bump lodash from 4.17.4 to 4.17.23 in /PerformanceTests/Speedometer/resources/todomvc/architecture-examples/react #18
Conversation
Bumps [lodash](https://github.com/lodash/lodash) from 4.17.4 to 4.17.23. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.4...4.17.23) --- updated-dependencies: - dependency-name: lodash dependency-version: 4.17.23 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
|
|
![semgrep-code-squarespace[bot]](https://avatars.githubusercontent.com/u/722929?s=60&v=4){kind=small}
| }, | ||
| "ua-parser-js": { | ||
| "node_modules/ua-parser-js": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 2931 lists a dependency (ua-parser-js) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of ua-parser-js are vulnerable to Uncontrolled Resource Consumption. UAParser.js uses a vulnerable regular expression to parse User-Agent headers. A malicious header can trigger catastrophic backtracking in the regex, resulting in prolonged processing times and potential denial of service.
To resolve this comment:
Check if you are using ua-parser-js via npx cli.
- If you're affected, upgrade this dependency to at least version 0.7.24 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/react/package-lock.json.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| }, | ||
| "ua-parser-js": { | ||
| "node_modules/ua-parser-js": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 2931 lists a dependency (ua-parser-js) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of ua-parser-js are vulnerable to Uncontrolled Resource Consumption. A specially crafted user agent string can trigger catastrophic backtracking in the regex designed for Redmi Phones and Mi Pad Tablets. This may result in a Regular Expression Denial of Service, causing resource exhaustion when ua-parser-js attempts to parse the malicious input.
To resolve this comment:
Check if you are using ua-parser-js via npx cli.
- If you're affected, upgrade this dependency to at least version 0.7.22 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/react/package-lock.json.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| }, | ||
| "ua-parser-js": { | ||
| "node_modules/ua-parser-js": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 2931 lists a dependency (ua-parser-js) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of ua-parser-js are vulnerable to Uncontrolled Resource Consumption. UAParser.js is vulnerable to Regular Expression Denial of Service (ReDoS) attacks. Maliciously crafted user agent strings can trigger inefficient regex patterns, leading to excessive backtracking and high CPU consumption, which may ultimately cause service degradation or a denial of service.
To resolve this comment:
Check if you are using ua-parser-js via npx cli.
- If you're affected, upgrade this dependency to at least version 0.7.23 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/react/package-lock.json.
- If you're not affected, comment
/fp we don't use this [condition]
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", | ||
| "dev": true | ||
| }, | ||
| "node_modules/fsevents": { |
There was a problem hiding this comment.
🔴 Malicious dependency detected blocking your code—remove immediately
The dependency fsevents contains malicious code and is a critical security risk. Remove it from your project immediately.
ℹ️ Why this matters
This specific version of fsevents contains malicious code. Upgrade to the safe version immediately.
References: https://osv.dev/vulnerability/MAL-2023-462
To resolve this comment:
Remove the dependency.
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| "ms": "2.0.0" | ||
| } | ||
| }, | ||
| "node_modules/fsevents/node_modules/deep-extend": { |
There was a problem hiding this comment.
Critical severity vulnerability introduced by a package you're using:
Line 1002 lists a dependency (deep-extend) with a known Critical severity vulnerability. Fixing requires upgrading or replacing the dependency.
ℹ️ Why this matters
Affected version of deep-extend is vulnerable to Prototype Pollution. Malicious input passed to deep-extend allows an attacker to overwrite the prototype of Object, polluting all JavaScript objects with arbitrary properties. This can lead to Denial of Service or even Remote Code Execution.
To resolve this comment:
Upgrade this dependency to at least version 0.5.1 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/react/package-lock.json.
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| } | ||
| }, | ||
| "babel-traverse": { | ||
| "node_modules/babel-traverse": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 331 lists a dependency (babel-traverse) with a known Critical severity vulnerability.
ℹ️ Why this matters
Affected versions of @babel/traverse, babel-traverse, @babel/plugin-transform-runtime, @babel/preset-env, @babel/helper-define-polyfill-provider, babel-plugin-polyfill-corejs2, babel-plugin-polyfill-corejs3, babel-plugin-polyfill-es-shims, and babel-plugin-polyfill-regenerator are vulnerable to Incomplete List Of Disallowed Inputs. An attacker can exploit a vulnerability in the internal Babel methods path.evaluate() or path.evaluateTruthy() by compiling specially crafted code, potentially resulting in arbitrary code execution during compilation. babel-traverse does not have a fix version. If you are using babel-traverse, switch to @babel/traverse.
To resolve this comment:
Check if you use Babel to compile untrusted JavaScript.
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
| "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", | ||
| "dev": true | ||
| }, | ||
| "node_modules/fsevents": { |
There was a problem hiding this comment.
Critical severity vulnerability introduced by a package you're using:
Line 694 lists a dependency (fsevents) with a known Critical severity vulnerability. Fixing requires upgrading or replacing the dependency.
ℹ️ Why this matters
Affected versions of fsevents are vulnerable to Improper Control Of Generation Of Code ('Code Injection'). fsevents depends on the https://fsevents-binaries.s3-us-west-2.amazonaws.com URL. If an attacker at any point gains control of this URL, they can execute arbitrary code on any JavaScript project that depends on fsevents or uses code distributed from this URL.
To resolve this comment:
Upgrade this dependency to at least version 1.2.11 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/react/package-lock.json.
💬 Ignore this finding
To ignore this, reply with:
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasons
You can view more details on this finding in the Semgrep AppSec Platform here.
Bumps lodash from 4.17.4 to 4.17.23.
Commits
dec55b7Bump main to v4.17.23 (#6088)19c9251fix: setCacheHas JSDoc return type should be boolean (#6071)b5e6729jsdoc: Add -0 and BigInt zeros to _.compact falsey values list (#6062)edadd45Prevent prototype pollution on baseUnset function4879a7adoc: fix autoLink function, conversion of source links (#6056)9648f69chore: removeyarn.lockfile (#6053)dfa407dci: remove legacy configuration files (#6052)156e196feat: add renovate setup (#6039)933e106ci: add pipeline for Bun (#6023)072a807docs: update links related to Open JS Foundation (#5968)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.