Closed renovate[bot] closed 6 months ago
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
â» Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @angular/cdk@14.2.4
npm ERR! Found: @angular/common@17.3.0
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"17.3.0" from the root project
npm ERR! peer @angular/common@"17.3.0" from @angular/forms@17.3.0
npm ERR! node_modules/@angular/forms
npm ERR! @angular/forms@"17.3.0" from the root project
npm ERR! 5 more (@angular/platform-browser, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^14.0.0 || ^15.0.0" from @angular/cdk@14.2.4
npm ERR! node_modules/@angular/cdk
npm ERR! peer @angular/cdk@">=14.0.0" from ng2-charts@4.1.1
npm ERR! node_modules/ng2-charts
npm ERR! ng2-charts@"4.1.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @angular/common@15.2.10
npm ERR! node_modules/@angular/common
npm ERR! peer @angular/common@"^14.0.0 || ^15.0.0" from @angular/cdk@14.2.4
npm ERR! node_modules/@angular/cdk
npm ERR! peer @angular/cdk@">=14.0.0" from ng2-charts@4.1.1
npm ERR! node_modules/ng2-charts
npm ERR! ng2-charts@"4.1.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-26T00_58_46_047Z-debug-0.log
This PR contains the following updates:
4.18.3
->4.19.2
GitHub Vulnerability Alerts
CVE-2024-29041
Impact
Versions of Express.js prior to 4.19.2 and pre-release alpha and beta versions before 5.0.0-beta.3 are affected by an open redirect vulnerability using malformed URLs.
When a user of Express performs a redirect using a user-provided URL Express performs an encode using
encodeurl
on the contents before passing it to thelocation
header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.The main method impacted is
res.location()
but this is also called from withinres.redirect()
.Patches
https://github.com/expressjs/express/commit/0867302ddbde0e9463d0564fea5861feb708c2dd https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94
An initial fix went out with
express@4.19.0
, we then patched a feature regression in4.19.1
and added improved handling for the bypass in4.19.2
.Workarounds
The fix for this involves pre-parsing the url string with either
require('node:url').parse
ornew URL
. These are steps you can take on your own before passing the user input string tores.location
orres.redirect
.References
https://github.com/expressjs/express/pull/5539 https://github.com/koajs/koa/issues/1800 https://expressjs.com/en/4x/api.html#res.location
Release Notes
expressjs/express (express)
### [`v4.19.2`](https://togithub.com/expressjs/express/blob/HEAD/History.md#4192--2024-03-25) [Compare Source](https://togithub.com/expressjs/express/compare/4.19.1...4.19.2) \========== - Improved fix for open redirect allow list bypass ### [`v4.19.1`](https://togithub.com/expressjs/express/blob/HEAD/History.md#4191--2024-03-20) [Compare Source](https://togithub.com/expressjs/express/compare/4.19.0...4.19.1) \========== - Allow passing non-strings to res.location with new encoding handling checks ### [`v4.19.0`](https://togithub.com/expressjs/express/compare/4.18.3...83e77aff6a3859d58206f3ff9501277023c03f87) [Compare Source](https://togithub.com/expressjs/express/compare/4.18.3...4.19.0)Configuration
đ Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
đŠ Automerge: Enabled.
â» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
đ Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.