Bump webpack-dev-server from 1.16.5 to 5.2.4 in /Websites/browserbench.org/Speedometer2.0/resources/todomvc/architecture-examples/preact#180
Conversation
Bumps [webpack-dev-server](https://github.com/webpack/webpack-dev-server) from 1.16.5 to 5.2.4. - [Release notes](https://github.com/webpack/webpack-dev-server/releases) - [Changelog](https://github.com/webpack/webpack-dev-server/blob/main/CHANGELOG.md) - [Commits](webpack/webpack-dev-server@v1.16.5...v5.2.4) --- updated-dependencies: - dependency-name: webpack-dev-server dependency-version: 5.2.4 dependency-type: direct:development ... 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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
You can view more details on this finding in the Semgrep AppSec Platform here.
| "node_modules/fsevents/node_modules/wide-align": { | ||
| "version": "1.1.2", | ||
| "resolved": "https://registry.npmjs.org/wide-align/-/wide-align-1.1.2.tgz", | ||
|
|
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 7646 lists a dependency (rollup) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of rollup are vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). Rollup is vulnerable to arbitrary file write via path traversal: chunk/asset names derived from user-controlled inputs (e.g., CLI named inputs, manual chunk aliases, or malicious plugins) are insufficiently sanitized, allowing ../ sequences to survive and be passed into path.resolve when computing output paths. This lets an attacker escape the configured output directory and overwrite arbitrary files on the host filesystem that the build process can write to, potentially leading to persistent RCE by clobbering shell/profile or other executable/config files.
To resolve this comment:
Check if you are running rollup --input.
- If you're affected, upgrade this dependency to at least version 2.80.0 at Websites/browserbench.org/Speedometer2.0/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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
You can view more details on this finding in the Semgrep AppSec Platform here.
| "node": ">= 0.4" | ||
| } | ||
| }, | ||
| "node_modules/ecstatic": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 3142 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.0/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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
You can view more details on this finding in the Semgrep AppSec Platform here.
| "node": ">= 0.4" | ||
| } | ||
| }, | ||
| "node_modules/ecstatic": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 3142 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.0/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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
You can view more details on this finding in the Semgrep AppSec Platform here.
| "node_modules/fsevents/node_modules/wide-align": { | ||
| "version": "1.1.2", | ||
| "resolved": "https://registry.npmjs.org/wide-align/-/wide-align-1.1.2.tgz", | ||
|
|
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 7646 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.0/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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
You can view more details on this finding in the Semgrep AppSec Platform here.
| "lodash": "^4.17.4" | ||
| } | ||
| }, | ||
| "node_modules/babel-traverse": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 2156 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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
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 3980 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.0/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
Questions about this? Check out our documentation on triaging findings and using Semgrep, or post questions in #security on Slack.
You can view more details on this finding in the Semgrep AppSec Platform here.
1 participant
Bumps webpack-dev-server from 1.16.5 to 5.2.4.
Release notes
Sourced from webpack-dev-server's releases.
... (truncated)
Changelog
Sourced from webpack-dev-server's changelog.
... (truncated)
Commits
fd40130chore(release): 5.2.4ece4f36chore: update deps (#5661)a216144ci: fix test (#5658)df073c5Merge commit from forkb550a70chore(release): 5.2.39704dc5chore: upgrade selfsigned to v5 and remove node-forge dependency (#5618)92bf644chore: bump express to update qs (#5621)792b2f0chore(deps-dev): bump the dependencies group with 4 updates (#5606)6d587cachore(deps): bump the dependencies group across 1 directory with 27 updates (...f91baa8fix(overlay): add ESC key to dismiss overlay (#5598)Maintainer changes
This version was pushed to npm by evilebottnawi, a new releaser for webpack-dev-server since your current version.
Install script changes
This version adds
preparescript that runs during installation. Review the package contents before updating.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 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.