Bump @angular/core from 4.3.1 to 19.2.19 in /Websites/browserbench.org/Speedometer2.0/resources/todomvc/architecture-examples/angular#59
Conversation
Bumps [@angular/core](https://github.com/angular/angular/tree/HEAD/packages/core) from 4.3.1 to 19.2.19. - [Release notes](https://github.com/angular/angular/releases) - [Changelog](https://github.com/angular/angular/blob/main/CHANGELOG.md) - [Commits](https://github.com/angular/angular/commits/v19.2.19/packages/core) --- updated-dependencies: - dependency-name: "@angular/core" dependency-version: 19.2.19 dependency-type: direct:production ... 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.8" | ||
| } | ||
| }, | ||
| "node_modules/karma": { |
There was a problem hiding this comment.
Medium severity vulnerability introduced by a package you're using:
Line 6079 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 Websites/browserbench.org/Speedometer2.0/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.0.0", | ||
| "resolved": "https://registry.npmjs.org/fs.realpath/-/fs.realpath-1.0.0.tgz", | ||
| "integrity": "sha1-FQStJSMVjKpA20onh8sBQRmU6k8=", | ||
| "dev": true | ||
| }, | ||
| "fsevents": { | ||
| "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.
| } | ||
| }, | ||
| "@angular/compiler": { | ||
| "node_modules/@angular/compiler": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 134 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 Websites/browserbench.org/Speedometer2.0/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.
| } | ||
| }, | ||
| "webpack-dev-server": { | ||
| "node_modules/webpack-dev-server": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 10632 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.0/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.
| } | ||
| }, | ||
| "http-proxy": { | ||
| "node_modules/http-proxy": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 5027 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.0/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.
| } | ||
| }, | ||
| "babel-traverse": { | ||
| "node_modules/babel-traverse": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 819 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.
| "node": ">=0.8.0" | ||
| } | ||
| }, | ||
| "node_modules/handlebars/node_modules/uglify-js": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 4710 lists a dependency (uglify-js) with a known Critical severity vulnerability.
ℹ️ Why this matters
uglify-js 2.x before 2.4.24 is vulnerable to Incorrect Comparison Logic Granularity which may cause crafted JavaScript to have altered functionality after minification.
To resolve this comment:
Check if you are using uglifyjs on CLI to minify.
- If you're affected, upgrade this dependency to at least version 2.4.24 at Websites/browserbench.org/Speedometer2.0/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.
| }, | ||
| "deep-extend": { | ||
| "node_modules/deep-extend": { |
There was a problem hiding this comment.
Critical severity vulnerability introduced by a package you're using:
Line 2153 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/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.
1 participant
Bumps @angular/core from 4.3.1 to 19.2.19.
Release notes
Sourced from
@angular/core's releases.... (truncated)
Changelog
Sourced from
@angular/core's changelog.... (truncated)
Commits
7475487fix(core): block creation of sensitive URI attributes from ICU messages26cdc53fix(core): sanitize sensitive attributes on SVG script elements7c42e2efix(compiler): prevent XSS via SVG animationattributeNameand MathML/SVG URLs70d0639fix(core): introduceBootstrapContextfor improved server bootstrapping (#6...73d3e00build: fix failing test (#61683)9e1cd49fix(migrations): preserve comments when removing unused imports (#61674)a6d5479build: migrate platform-server to rules_js (#61619)2a26944build: migrate platform-browser and platform-browser-dynamic package to use r...2ae69f7refactor: ensure tsurge migrations have clear ownership of files (#61612)c101a3arefactor: clean-up deduplication workaround from migrations (#61421) (#61612)Maintainer changes
This version was pushed to npm by google-wombot, a new releaser for
@angular/coresince your current version.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.