Bump lodash.template from 4.4.0 to 4.18.1 in /PerformanceTests/Speedometer/resources/todomvc/architecture-examples/emberjs#120
Conversation
Bumps [lodash.template](https://github.com/lodash/lodash) from 4.4.0 to 4.18.1. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.4.0...4.18.1) --- updated-dependencies: - dependency-name: lodash.template dependency-version: 4.18.1 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}
| "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.
| "version": "1.3.0", | ||
| "resolved": "https://registry.npmjs.org/growly/-/growly-1.3.0.tgz", | ||
| "integrity": "sha1-8QdIy+dq+WS3yWyTxrzCivEgwIE=", | ||
| "dev": true | ||
| }, | ||
| "handlebars": { | ||
| "node_modules/handlebars": { |
There was a problem hiding this comment.
High severity vulnerability may affect your project—review required:
Line 5379 lists a dependency (handlebars) with a known High severity vulnerability.
ℹ️ Why this matters
Affected versions of handlebars are vulnerable to Improper Control of Generation of Code ('Code Injection') / Improper Encoding or Escaping of Output / Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). The Handlebars CLI precompiler allows arbitrary JavaScript injection by embedding unescaped template filenames and CLI option values such as --namespace, --commonjs, and --handlebarPath directly into generated output. An attacker who can control these inputs can cause malicious code to execute when the precompiled bundle is loaded in Node.js or a browser.
To resolve this comment:
Check if you execute templates through the Handlebars CLI precompiler.
- If you're affected, upgrade this dependency to at least version 4.7.9 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/emberjs/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 5610 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/emberjs/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.
| } | ||
| }, | ||
| "tmpl": { | ||
| "node_modules/tmpl": { |
There was a problem hiding this comment.
High severity vulnerability introduced by a package you're using:
Line 8525 lists a dependency (tmpl) with a known High severity vulnerability. Fixing requires upgrading or replacing the dependency.
ℹ️ Why this matters
tmpl versions before 1.0.5 are vulnerable to Uncontrolled Resource Consumption when formatting a string.
To resolve this comment:
Upgrade this dependency to at least version 1.0.5 at PerformanceTests/Speedometer/resources/todomvc/architecture-examples/emberjs/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.
| "integrity": "sha1-eCA6TRwyiuHYbcpkYONptX9AVa4=", | ||
| "dev": true | ||
| }, | ||
| "node_modules/babel-traverse": { |
There was a problem hiding this comment.
Critical severity vulnerability may affect your project—review required:
Line 784 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 4232 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/emberjs/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 lodash.template from 4.4.0 to 4.18.1.
Release notes
Sourced from lodash.template's releases.
Commits
cb0b9b9release(patch): bump main to 4.18.1 (#6177)75535f5chore: prune stale advisory refs (#6170)62e91bcdocs: remove n_ Node.js < 6 REPL note from README (#6165)59be2derelease(minor): bump to 4.18.0 (#6161)af63457fix: broken tests for _.template 879aaa91073a76fix: linting issues879aaa9fix: validate imports keys in _.templatefe8d32efix: block prototype pollution in baseUnset via constructor/prototype traversal18ba0a3refactor(fromPairs): use baseAssignValue for consistent assignment (#6153)b819080ci: add dist sync validation workflow (#6137)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.