Bump minimatch from 3.0.4 to 3.1.5 in /Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact#62
Conversation
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.0.4 to 3.1.5. - [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md) - [Commits](isaacs/minimatch@v3.0.4...v3.1.5) --- updated-dependencies: - dependency-name: minimatch dependency-version: 3.1.5 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}
| "node": ">= 0.6" | ||
| } | ||
| }, | ||
| "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.
| } | ||
| }, | ||
| "postcss-minify-selectors": { | ||
| "node_modules/postcss-minify-selectors": { | ||
| "version": "2.1.1", | ||
| "resolved": "https://registry.npmjs.org/postcss-mi |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 6555 lists a dependency (webpack-dev-server) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of webpack-dev-server are vulnerable to Improper Input Validation. Missing origin validation on webpack-dev-server's Hot Module Replacement websocket allows any webpage to connect to the dev server's socket, access in‐memory compiled assets and source code, and exfiltrate a developer's source files.
To resolve this comment:
Check if you are using webpack-dev-server with Hot Module Replacement enabled (i.e. using the --hot argument).
- If you're affected, upgrade this dependency to at least version 3.1.11 at Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact/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.
| }, | ||
| "ecstatic": { | ||
| "node_modules/ecstatic": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 1968 lists a dependency (ecstatic) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of ecstatic are vulnerable to URL Redirection to Untrusted Site ('Open Redirect'). An open redirect exists in ecstatic’s redirect logic: it does not validate the target of its HTTP 301 redirects (used for directory slashes or default‐extension lookups), allowing an attacker to craft a URL that causes ecstatic to redirect clients to an arbitrary external domain. This ecstatic package is unmaintained and deprecated.
To resolve this comment:
Check if you running ecstatic as standalone server through the Command Line Interface.
- If you're affected, upgrade this dependency to at least version 2.2.2 at Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact/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.
| }, | ||
| "ecstatic": { | ||
| "node_modules/ecstatic": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 1968 lists a dependency (ecstatic) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of ecstatic are vulnerable to Uncontrolled Resource Consumption. An attacker can send specially crafted requests that trigger a Regular Expression Denial of Service (ReDoS), causing the server to use excessive memory or CPU and potentially crash. This ecstatic package is unmaintained and deprecated
To resolve this comment:
Check if you running ecstatic as standalone server through the Command Line Interface.
- If you're affected, upgrade this dependency to at least version 2.0.0 at Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact/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.
| } | ||
| }, | ||
| "http-proxy": { | ||
| "node_modules/http-proxy": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 3859 lists a dependency (http-proxy) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of http-proxy are vulnerable to Incomplete List of Disallowed Inputs / Protection Mechanism Failure. A denial-of-service exists in node-http-proxy when using proxyReq.setHeader: an HTTP request with a body longer than ~1024 bytes triggers an unhandled ERR_HTTP_HEADERS_SENT exception that crashes the proxy server.
References: GHSA
To resolve this comment:
Check if you set headers on the proxy request using the proxyReq.setHeader function in a standalone proxy server implemented using the http-proxy package.
- If you're affected, upgrade this dependency to at least version 1.18.1 at Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact/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.
| } | ||
| }, | ||
| "postcss-minify-selectors": { | ||
| "node_modules/postcss-minify-selectors": { | ||
| "version": "2.1.1", | ||
| "resolved": "https://registry.npmjs.org/postcss-mi |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 5811 lists a dependency (rollup) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of rollup are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
To resolve this comment:
Check if you use Rollup to bundle JavaScript with import.meta.url and the output format is set to cjs, umd, or iife formats, while allowing users to inject scriptless HTML elements with unsanitized name attributes.
- If you're affected, upgrade this dependency to at least version 2.79.2 at Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact/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.
| } | ||
| }, | ||
| "babel-traverse": { | ||
| "node_modules/babel-traverse": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 1256 lists a dependency (babel-traverse) with a known Critical severity vulnerability.
ℹ️ Why this matters
Affected versions of @babel/traverse and babel-traverse are vulnerable to Incomplete List of Disallowed Inputs / Incorrect Comparison. Compiling untrusted code with Babel using plugins that invoke the internal path.evaluate() or path.evaluateTruthy() methods (for example @babel/plugin-transform-runtime, @babel/preset-env with useBuiltIns, or any polyfill‐provider plugin) allows a maliciously crafted AST to execute arbitrary code on the build machine during compilation.
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.
| "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 2675 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 Websites/browserbench.org/Speedometer2.1/resources/todomvc/architecture-examples/preact/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.
1 participant
Bumps minimatch from 3.0.4 to 3.1.5.
Commits
7bba9783.1.5bd25942docs: add warning about ReDoS1a9c27cfix partial matching of globstar patterns1a2e0843.1.4ae24656update lockfileb100374limit recursion for **, improve perf considerably26ffeaalockfile update9eca892lock node version to 1400c323b3.1.330486b2update CI matrix and actionsDependabot 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 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.