passing untrusted user input - even after sanitizing it - to SendStream.redirect() may execute untrusted code
Patches
this issue is patched in send 0.19.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
The attacker MUST control the input to response.redirect()
express MUST NOT redirect before the template appears
the browser MUST NOT complete redirection before:
the user MUST click on the link in the template
Release Notes
pillarjs/send (send)
### [`v0.19.0`](https://redirect.github.com/pillarjs/send/blob/HEAD/HISTORY.md#0190--2024-09-10)
[Compare Source](https://redirect.github.com/pillarjs/send/compare/0.18.0...0.19.0)
\===================
- Remove link renderization in html while redirecting
### [`v0.18.0`](https://redirect.github.com/pillarjs/send/blob/HEAD/HISTORY.md#0180--2022-03-23)
[Compare Source](https://redirect.github.com/pillarjs/send/compare/0.17.2...0.18.0)
\===================
- Fix emitted 416 error missing headers property
- Limit the headers removed for 304 response
- deps: depd@2.0.0
- Replace internal `eval` usage with `Function` constructor
- Use instance methods on `process` to check for listeners
- deps: destroy@1.2.0
- deps: http-errors@2.0.0
- deps: depd@2.0.0
- deps: statuses@2.0.1
- deps: on-finished@2.4.1
- deps: statuses@2.0.1
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
^0.17.1->^0.19.0GitHub Vulnerability Alerts
CVE-2024-43799
Impact
passing untrusted user input - even after sanitizing it - to
SendStream.redirect()may execute untrusted codePatches
this issue is patched in send 0.19.0
Workarounds
users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist
Details
successful exploitation of this vector requires the following:
Release Notes
pillarjs/send (send)
### [`v0.19.0`](https://redirect.github.com/pillarjs/send/blob/HEAD/HISTORY.md#0190--2024-09-10) [Compare Source](https://redirect.github.com/pillarjs/send/compare/0.18.0...0.19.0) \=================== - Remove link renderization in html while redirecting ### [`v0.18.0`](https://redirect.github.com/pillarjs/send/blob/HEAD/HISTORY.md#0180--2022-03-23) [Compare Source](https://redirect.github.com/pillarjs/send/compare/0.17.2...0.18.0) \=================== - Fix emitted 416 error missing headers property - Limit the headers removed for 304 response - deps: depd@2.0.0 - Replace internal `eval` usage with `Function` constructor - Use instance methods on `process` to check for listeners - deps: destroy@1.2.0 - deps: http-errors@2.0.0 - deps: depd@2.0.0 - deps: statuses@2.0.1 - deps: on-finished@2.4.1 - deps: statuses@2.0.1Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.