🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
In express <4.20.0, passing untrusted user input - even after sanitizing it - to response.redirect() may execute untrusted code
Patches
this issue is patched in express 4.20.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
body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service.
A bad regular expression is generated any time you have two parameters within a single segment, separated by something that is not a period (.). For example, /:a-:b.
Patches
For users of 0.1, upgrade to 0.1.10. All other users should upgrade to 8.0.0.
Version 0.1.10 adds backtracking protection when a custom regular expression is not provided, so it's still possible to manually create a ReDoS vulnerability if you are providing custom regular expressions.
Version 7.0.0 can enable strict: true and get an error when the regular expression might be bad.
Version 8.0.0 removes all features that can cause a ReDoS and stops exposing the regular expression directly.
Workarounds
All versions can be patched by providing a custom regular expression for parameters after the first in a single segment. As long as the custom regular expression does not match the text before the parameter, you will be safe. For example, change /:a-:b to /:a-:b([^-/]+).
If paths cannot be rewritten and versions cannot be upgraded, another alternative is to limit the URL length. For example, halving the attack string improves performance by 4x faster.
Details
Using /:a-:b will produce the regular expression /^\/([^\/]+?)-([^\/]+?)\/?$/. This can be exploited by a path such as /a${'-a'.repeat(8_000)}/a. OWASP has a good example of why this occurs, but the TL;DR is the /a at the end ensures this route would never match but due to naive backtracking it will still attempt every combination of the :a-:b on the repeated 8,000 -a.
Because JavaScript is single threaded and regex matching runs on the main thread, poor performance will block the event loop and can lead to a DoS. In local benchmarks, exploiting the unsafe regex will result in performance that is over 1000x worse than the safe regex. In a more realistic environment using Express v4 and 10 concurrent connections, this translated to average latency of ~600ms vs 1ms.
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
passing untrusted user input - even after sanitizing it - to redirect() may execute untrusted code
Patches
this issue is patched in serve-static 1.16.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
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu cancel merge
Cancels automatic merging of this PR
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ express (4.19.2 → 4.20.0) · Repo · Changelog
Security Advisories 🚨
🚨 express vulnerable to XSS via response.redirect()
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ body-parser (indirect, 1.20.2 → 1.20.3) · Repo · Changelog
Security Advisories 🚨
🚨 body-parser vulnerable to denial of service when url encoding is enabled
Commits
See the full diff on Github. The new version differs by 8 commits:
1.20.3
chore: linter (#534)
Merge commit from fork
add scorecard to readme (#531)
deps: qs@6.12.3 (#521)
fix: pin to node@22.4.1
ci: fix errors in ci github action for node 8 and 9 (#523)
chore: add support for OSSF scorecard reporting (#522)
↗️ call-bind (indirect, 1.0.2 → 1.0.7) · Repo · Changelog
Release Notes
1.0.7 (from changelog)
1.0.6 (from changelog)
1.0.5 (from changelog)
1.0.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 34 commits:
v1.0.7
[Refactor] use `es-define-property`
[Deps] update `get-intrinsic`, `set-function-length`
v1.0.6
[Refactor] use `es-errors`, so things that only need those do not need `get-intrinsic`
[meta] add missing `engines.node`
[Deps] update `get-intrinsic`, `set-function-length`
[Dev Deps] update `aud`, `npmignore`, `tape`
v1.0.5
[Deps] update `set-function-length`
[Fix] throw an error on non-functions as early as possible
v1.0.4
v1.0.3
[Refactor] use `set-function-length`
[Deps] update `define-data-property`, `function-bind`, `get-intrinsic`
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`
[Deps] update `get-intrinsic`
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`
[Deps] update `get-intrinsic`
[Dev Deps] update `aud`, `tape`
[actions] update checkout action
[meta] use `npmignore` to autogenerate an npmignore file
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `tape`
[Deps] update `get-intrinsic`
[actions] reuse common workflows
[meta] simplify "exports"
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `safe-publish-latest`, `tape`
[readme] flesh out content
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `safe-publish-latest`, `tape`
[actions] update codecov uploader
[Deps] update `get-intrinsic`
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`
[actions] use `node/install` instead of `node/run`; use `codecov` action
[meta] use `prepublishOnly` script for npm 7+
↗️ get-intrinsic (indirect, 1.1.3 → 1.2.4) · Repo · Changelog
Release Notes
1.2.4 (from changelog)
1.2.3 (from changelog)
1.2.2 (from changelog)
1.2.1 (from changelog)
1.2.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 25 commits:
v1.2.4
[Refactor] use all 7 <+ ES6 Errors from `es-errors`
v1.2.3
[Refactor] use `es-errors`, so things that only need those do not need `get-intrinsic`
[Dev Deps] update `tape`
[meta] add missing `engines.node`
[Robustness] use null objects for lookups
[Dev Deps] update `aud`, `es-abstract`, `mock-property`, `npmignore`
[meta] simplify `exports`
[meta] add `sideEffects` flag
v1.2.2
[Refactor] use `hasown` instead of `has`
[Deps] update `function-bind`
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `call-bind`, `es-abstract`, `mock-property`, `object-inspect`, `tape`
v1.2.1
[Fix] avoid a crash in envs without `__proto__`
[Dev Deps] update `es-abstract`
v1.2.0
[New] add `BigInt64Array` and `BigUint64Array`
[Dev Deps] update `@ljharb/eslint-config`, `es-abstract`, `object-inspect`, `tape`
[Fix] ensure `Error.prototype` is undeniable
[Dev Deps] update `aud`, `es-abstract`
[Tests] use `gopd`
[Dev Deps] update `aud`, `es-abstract`, `tape`
[actions] update checkout action
↗️ merge-descriptors (indirect, 1.0.1 → 1.0.3) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 34 commits:
1.0.3
Update repo URL
build: Node.js@10.15
build: Node.js@8.15
build: Node.js@6.16
Fix typo in code comment
build: run coverage reports on more versions
build: mocha@5.2.0
build: restructure Travis CI build steps
build: use nyc for test coverage
lint: apply standard 12 style
tests: use strict equality
build: Node.js@10.13
build: Node.js@8.12
build: eslint-plugin-import@2.14.0
build: Node.js@10.7
build: use yaml eslint configuration
build: support Node.js 10.x
tests: fix throw asserts
lint: apply standard 11 style
docs: use module name as readme title
docs: document return value
build: Node.js@8.11
build: Node.js@6.14
build: Node.js@4.9
build: support Node.js 9.x
build: cache node_modules on Travis CI
build: support Node.js 8.x
build: support Node.js 7.x
build: use precise dist for Travis CI
build: support Node.js 6.x
build: Node.js@5.12
build: Node.js@4.8
build: istanbul@0.4.5
↗️ object-inspect (indirect, 1.12.2 → 1.13.2) · Repo · Changelog
Release Notes
1.13.2 (from changelog)
1.13.1 (from changelog)
1.13.0 (from changelog)
1.12.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 28 commits:
v1.13.2
[readme] update badges
[Dev Deps] update `@ljharb/eslint-config`, `tape`
[Fix] Don't throw when `global` is not defined
[Dev Deps] update `globalthis`
[Dev Deps] update `error-cause`
[Dev Deps] update `error-cause`, `has-tostringtag`, `tape`
[meta] add missing `engines.node`
[Dev Deps] update `npmignore`
[Dev Deps] update `mock-property`
[Dev Deps] update `tape`
v1.13.1
[Fix] in IE 8, global can !== window despite them being prototypes of each other
v1.13.0
[Dev Deps] update `error-cause`
[Dev Deps] temporarily remove `aud` due to breaking change in transitive deps
[New] add special handling for the global object
[Dev Deps] pin `glob`, since v10.3.8+ requires a broken `jackspeak`
[Dev Deps] update `mock-property`, `tape`
[Dev Deps] update `tape`
[Dev Deps] pin `jackspeak` since 2.1.2+ depends on npm aliases, which kill the install process in npm < 6
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`
v1.12.3
[Fix] in eg FF 24, collections lack forEach
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `error-cause`
[Dev Deps] update `aud`, `es-value-fixtures`, `tape`
[actions] update rebase action to use reusable workflow
[Tests] add `@pkgjs/support` to `postlint`
↗️ path-to-regexp (indirect, 0.1.7 → 0.1.10) · Repo · Changelog
Security Advisories 🚨
🚨 path-to-regexp outputs backtracking regular expressions
Release Notes
0.1.10
0.1.9
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 7 commits:
0.1.10
Add backtrack protection to parameters
Update repo url (#314)
0.1.9
Allow a non-lookahead regex (#312)
0.1.8
Add support for named matching groups (#301)
↗️ send (indirect, 0.18.0 → 0.19.0) · Repo · Changelog
Security Advisories 🚨
🚨 send vulnerable to template injection that can lead to XSS
Commits
See the full diff on Github. The new version differs by 2 commits:
0.19.0
Merge commit from fork
↗️ serve-static (indirect, 1.15.0 → 1.16.0) · Repo · Changelog
Security Advisories 🚨
🚨 serve-static vulnerable to template injection that can lead to XSS
Commits
See the full diff on Github. The new version differs by 2 commits:
1.16.0
Merge commit from fork
↗️ side-channel (indirect, 1.0.4 → 1.0.6) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 22 commits:
v1.0.6
add types
[meta] simplify `exports`
[Deps] update `call-bind`
[Dev Deps] update `tape`
v1.0.5
[Deps] update `get-intrinsic`
[meta] add missing `engines.node`
[Refactor] use `es-errors`, so things that only need those do not need `get-intrinsic`
[Deps] update `call-bind`, `get-intrinsic`, `object-inspect`
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `npmignore`, `tape`
[Deps] update `get-intrinsic`, `object-inspect`
[meta] use `npmignore` to autogenerate an npmignore file
[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`
[actions] update rebase action
[Tests] increase coverage
[meta] add `.editorconfig`; add `eclint`
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `tape`
[Deps] update `object-inspect`
[actions] reuse common workflows
[Deps] update `call-bind`, `get-intrinsic`, `object-inspect`
[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`, `safe-publish-latest`, `tape`
🆕 define-data-property (added, 1.1.4)
🆕 es-define-property (added, 1.0.0)
🆕 es-errors (added, 1.3.0)
🆕 gopd (added, 1.0.1)
🆕 has-property-descriptors (added, 1.0.2)
🆕 has-proto (added, 1.0.3)
🆕 set-function-length (added, 1.2.2)
🗑️ has (removed)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands