Bump tar, @angular/cli and fsevents in /PerformanceTests/Speedometer/resources/todomvc/architecture-examples/angular #15
Conversation
Bumps [tar](https://github.com/isaacs/node-tar) to 7.5.6 and updates ancestor dependencies [tar](https://github.com/isaacs/node-tar), [@angular/cli](https://github.com/angular/angular-cli) and [fsevents](https://github.com/fsevents/fsevents). These dependencies need to be updated together. Updates `tar` from 2.2.1 to 7.5.6 - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v2.2.1...v7.5.6) Updates `@angular/cli` from 1.0.0 to 21.1.0 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md) - [Commits](angular/angular-cli@v1.0.0...v21.1.0) 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) --- updated-dependencies: - dependency-name: tar dependency-version: 7.5.6 dependency-type: indirect - dependency-name: "@angular/cli" dependency-version: 21.1.0 dependency-type: direct:development - dependency-name: fsevents dependency-version: 1.2.13 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_modules/express/node_modules/statuses": { | ||
| "version": "2.0.2", | ||
| "resolved": "https://registry.npmjs.org/statuses/-/statuses-2.0.2.tgz", | ||
| "integrity": "sha512-DvEy55V3DB7uknRo+4iOGT5fP1slR8wQo |
There was a problem hiding this comment.
Medium severity vulnerability introduced by a package you're using:
Line 6025 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/Speedometer/resources/todomvc/architecture-examples/angular/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.
| "node_modules/express/node_modules/statuses": { | ||
| "version": "2.0.2", | ||
| "resolved": "https://registry.npmjs.org/statuses/-/statuses-2.0.2.tgz", | ||
| "integrity": "sha512-DvEy55V3DB7uknRo+4iOGT5fP1slR8wQo |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 5114 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/Speedometer/resources/todomvc/architecture-examples/angular/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.
| "balanced-match": "1.0.0", | ||
| "concat-map": "0.0.1" | ||
| }, | ||
| "node_modules/@angular/compiler": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 1044 lists a dependency (@angular/compiler) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of @angular/compiler are vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). A stored XSS vulnerability in the Angular Template Compiler arises because its internal security schema doesn't classify certain URL‐ holding attributes (e.g. xlink:href, math|href, annotation|href) or the attributeName binding on SVG animation elements (<animate>, <set>, etc.) as requiring strict URL sanitization. An attacker who can supply untrusted input to template bindings like [attr.xlink:href] or <animate [attributeName]="'href'" [values]="maliciousURL"> can inject a javascript: URL payload. When the element is activated (e.g. clicked) or the animation runs, the malicious script executes in the application's origin, enabling session hijacking, data exfiltration, or unauthorized actions.
To resolve this comment:
Check if you allow SVG/MathML attributes (e.g., xlink:href, href) or to the attributeName field of SVG animation tags (, , etc.) in HTML templates.
- If you're affected, upgrade this dependency to at least version 19.2.17 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/angular/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.
| "node": ">=0.10.0" | ||
| } | ||
| }, | ||
| "node_modules/deep-extend": { |
There was a problem hiding this comment.
Critical severity vulnerability introduced by a package you're using:
Line 3516 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/angular/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.
| "version": "1.8.2", | ||
| "resolved": "https://registry.npmjs.org/expand-range/-/expand-range-1.8.2.tgz", | ||
| "integrity": "sha1-opnv/TNf4nIeuujiV+x5ZE/IUzc=", | ||
| "node_modules/babel-traverse": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 2435 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.
Bumps tar to 7.5.6 and updates ancestor dependencies tar, @angular/cli and fsevents. These dependencies need to be updated together.
Updates
tarfrom 2.2.1 to 7.5.6Release notes
Sourced from tar's releases.
Changelog
Sourced from tar's changelog.
... (truncated)
Commits
394ece67.5.67d4cc17fix race puting a Link ahead of its target File26ab9047.5.5e9a1ddbfix: do not prevent valid linkpaths within archive911c8867.5.43b1abfanormalize out unicode ligaturesa43478cremove some unused files970c58fupdate depsbb21974update changelog03138447.5.3Maintainer changes
This version was pushed to npm by isaacs, a new releaser for tar since your current version.
Updates
@angular/clifrom 1.0.0 to 21.1.0Release notes
Sourced from
@angular/cli's releases.... (truncated)
Changelog
Sourced from
@angular/cli's changelog.... (truncated)
Commits
9c5a2e3release: cut the v21.1.0 release94e7f49build: update Angular versions to 21.1.0 stable versions84a228cbuild: update dependency bazel to v8.5.19ae6844build: update dependency node to v22.22.009c5c9fbuild: lock file maintenance977d461refactor: update license URL from angular.io to angular.dev and angular mater...f13c845refactor: update copyright from Google Inc to Google LLC8d99cfefix(@angular/ssr): handle platform destruction during rendering8195bf8build: update cross-repo angular dependenciesd45693arefactor(@angular/cli): support copying config files to temp package directoryMaintainer changes
This version was pushed to npm by google-wombot, a new releaser for
@angular/clisince your current version.Updates
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)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.