Bump tar, fsevents and surge in /PerformanceTests/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack #21
Conversation
Removes [tar](https://github.com/isaacs/node-tar). It's no longer used after updating ancestor dependencies [tar](https://github.com/isaacs/node-tar), [fsevents](https://github.com/fsevents/fsevents) and [surge](https://github.com/sintaxi/surge). These dependencies need to be updated together. Removes `tar` Updates `fsevents` from 1.1.2 to 1.2.13 - [Release notes](https://github.com/fsevents/fsevents/releases) - [Commits](fsevents/fsevents@v1.1.2...v1.2.13) Updates `surge` from 0.18.0 to 0.24.6 - [Release notes](https://github.com/sintaxi/surge/releases) - [Commits](sintaxi/surge@v0.18.0...v0.24.6) --- updated-dependencies: - dependency-name: tar dependency-version: dependency-type: indirect - dependency-name: fsevents dependency-version: 1.2.13 dependency-type: indirect - dependency-name: surge dependency-version: 0.24.6 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}
| }, | ||
| "karma": { | ||
| "node_modules/karma": { |
There was a problem hiding this comment.
Medium severity vulnerability introduced by a package you're using:
Line 6259 lists a dependency (karma) with a known Medium severity vulnerability. Fixing requires upgrading or replacing the dependency.
ℹ️ Why this matters
karma 6.x before 6.3.14 is vulnerable to improper neutralization of input during web page generation ('cross-site scripting'). Karma does not enforce the HTTP protocol on the return_url query parameter which leads to reflected cross-site scripting when providing a URL like https://$KARMA_ROOT/?return_url=javascript:alert(document.domain). Upgrade to karma 6.3.14.
To resolve this comment:
Upgrade this dependency to at least version 6.3.14 at PerformanceTests/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack/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.
| "safer-buffer": "^2.1.0" | ||
| } | ||
| }, | ||
| "node_modules/ecstatic": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 3299 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 PerformanceTests/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack/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 5379 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 PerformanceTests/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack/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.
| "safer-buffer": "^2.1.0" | ||
| } | ||
| }, | ||
| "node_modules/ecstatic": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 3299 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 PerformanceTests/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack/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.
| "version": "0.0.6", | ||
| "resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz", | ||
| "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=", | ||
| "dev": true | ||
| }, | ||
| "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 10728 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/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack/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.
| "version": "0.0.6", | ||
| "resolved": "https://registry.npmjs.org/typedarray/-/typedarray-0.0.6.tgz", | ||
| "integrity": "sha1-hnrHTjhkGHsdPUfZlqeOxciDB3c=", | ||
| "dev": true | ||
| }, | ||
| "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 10728 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/Speedometer2.1/resources/todomvc/vanilla-examples/es2015-babel-webpack/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 1415 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.
1 participant
Removes tar. It's no longer used after updating ancestor dependencies tar, fsevents and surge. These dependencies need to be updated together.
Removes
tarUpdates
fseventsfrom 1.1.2 to 1.2.13Release notes
Sourced from fsevents's releases.
Commits
844a05dVersion Bumpf393f2aOnly build fsevents on macOS (#322)6a281a7[publish binary]acc2bce[publish binary]f532b6e[publish binary]4c6a1c0Add node 13 to travis matrix.92e40aaRelease 1.2.12.909af26Release v1.2.117074adbRelease v1.2.100a052f6Node.js v12 support for v1.x (#274)Updates
surgefrom 0.18.0 to 0.24.6Release notes
Sourced from surge's releases.
Commits
cf77cea0.24.68d3dab9updates surge-sdk, surge-stream01662100.24.53ab9fe6bumps surge-sdk, surge-stream v0.6.280337cd0.24.426772c7updates surge-sdk, surge-stream87c57b6removes old deployment script88633760.24.37886d83adds .npmignore6bd59940.24.2Dependabot 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.