This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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.
Pug through 3.0.2 allows JavaScript code execution if an application accepts untrusted input for the name option of the compileClient, compileFileClient, or compileClientWithDependenciesTracked function. NOTE: these functions are for compiling Pug templates into JavaScript, and there would typically be no reason to allow untrusted callers.
If a remote attacker was able to control the pretty option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.
Patches
Upgrade to pug@3.0.1 or pug-code-gen@3.0.2 or pug-code-gen@2.0.3, which correctly sanitise the parameter.
Workarounds
If there is no way for un-trusted input to be passed to pug as the pretty option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.
Affected versions of acorn are vulnerable to Regular Expression Denial of Service.
A regex in the form of /[x-\ud800]/u causes the parser to enter an infinite loop.
The string is not valid UTF16 which usually results in it being sanitized before reaching the parser.
If an application processes untrusted input and passes it directly to acorn,
attackers may leverage the vulnerability leading to Denial of Service.
Affected versions of acorn are vulnerable to Regular Expression Denial of Service.
A regex in the form of /[x-\ud800]/u causes the parser to enter an infinite loop.
The string is not valid UTF16 which usually results in it being sanitized before reaching the parser.
If an application processes untrusted input and passes it directly to acorn,
attackers may leverage the vulnerability leading to Denial of Service.
Affected versions of acorn are vulnerable to Regular Expression Denial of Service.
A regex in the form of /[x-\ud800]/u causes the parser to enter an infinite loop.
The string is not valid UTF16 which usually results in it being sanitized before reaching the parser.
If an application processes untrusted input and passes it directly to acorn,
attackers may leverage the vulnerability leading to Denial of Service.
Pug through 3.0.2 allows JavaScript code execution if an application accepts untrusted input for the name option of the compileClient, compileFileClient, or compileClientWithDependenciesTracked function. NOTE: these functions are for compiling Pug templates into JavaScript, and there would typically be no reason to allow untrusted callers.
If a remote attacker was able to control the pretty option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.
Patches
Upgrade to pug@3.0.1 or pug-code-gen@3.0.2 or pug-code-gen@2.0.3, which correctly sanitise the parameter.
Workarounds
If there is no way for un-trusted input to be passed to pug as the pretty option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.
If a remote attacker was able to control the pretty option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was possible for them to achieve remote code execution on the node.js backend.
Patches
Upgrade to pug@3.0.1 or pug-code-gen@3.0.2 or pug-code-gen@2.0.3, which correctly sanitise the parameter.
Workarounds
If there is no way for un-trusted input to be passed to pug as the pretty option, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.
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)
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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?
✳️ pug (2.0.4 → 3.0.3) · Repo · Changelog
Security Advisories 🚨
🚨 Pug allows JavaScript code execution if an application accepts untrusted input
🚨 Remote code execution via the `pretty` option.
↗️ acorn (indirect, 3.3.0 → 7.4.1) · Repo
Security Advisories 🚨
🚨 Regular Expression Denial of Service in Acorn
🚨 Regular Expression Denial of Service in Acorn
🚨 Regular Expression Denial of Service in Acorn
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
↗️ constantinople (indirect, 3.1.2 → 4.0.1) · Repo
Commits
See the full diff on Github. The new version differs by 5 commits:
Release 4.0.1Release 4.0.0chore: apply prettier and use actual expression type (#10)deps: update babylon -> @babel/parser, babel-types -> @babel/types (#9)Only allow es5 trailing commas in tests↗️ function-bind (indirect, 1.1.1 → 1.1.2) · Repo · Changelog
Commits
See the full diff on Github. The new version differs by 26 commits:
v1.1.2[meta] add `auto-changelog`[Robustness] remove runtime dependency on all builtins except `.apply`[Dev Deps] update `@ljharb/eslint-config`, `aud`, `tape`[meta] add `funding` field; create FUNDING.yml[Tests] use `aud` instead of `npm audit`[meta] update `.gitignore`[Tests] switch to nyc for coverage[meta] add `safe-publish-latest`[Dev Deps] update `@ljharb/eslint-config`, `tape`[actions] fix permissionsRevert "Point to the correct file"Merge pull request #16 from svedova/patch-1Point to the correct file[readme] update badges[meta] use `npmignore` to autogenerate an npmignore file[Tests] migrate tests to Github Actions[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape`[meta] create SECURITY.md[Tests] fix eslint errors from #15[Dev Deps] update `@ljharb/eslint‑config`, `eslint`, `tape`[Tests] up to `node` `v11.10`, `v10.15`, `v9.11`, `v8.15`, `v6.16`, `v4.9`; use `nvm install-latest-npm`; run audit script in tests[Tests] add `npm run audit`[Tests] remove `jscs`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `covert`, `tape`Docs: enable badges; update wording↗️ is-regex (indirect, 1.0.5 → 1.1.4) · Repo · Changelog
Release Notes
1.1.4 (from changelog)
1.1.3 (from changelog)
1.1.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 31 commits:
v1.1.4[Dev Deps] update `auto-changelog`, `core-js`, `eslint`, `tape`[Refactor] use `has-tostringtag` to behave correctly in the presence of symbol shamsv1.1.3[Fix] do not use `Object.prototype.toString` when `Symbol.toStringTag` is shammed[Deps] update `has-symbols`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[readme] add actions and codecov badges[actions] use `node/install` instead of `node/run`; use `codecov` action[meta] use `prepublishOnly` script for npm 7+v1.1.2[Robustness] use `call-bind`[meta] do not publish github action workflow files[readme] fix repo URLs; remove travis badge[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape`[meta] gitignore coverage output[actions] update workflows[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `auto-changelog`[Tests] migrate tests to Github Actions[Tests] run `nyc` on all tests[actions] add "Allow Edits" workflow[actions] switch Automatic Rebase workflow to `pull_request_target` eventv1.1.1[Dev Deps] update `auto-changelog`, `eslint`[Performance] Re-add lastIndex check to improve performancev1.1.0[New] use `badStringifier`‑based RegExp detection[meta] only run `aud` on prod deps[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `aud`, `tape`[Dev Deps] update `auto-changelog`, `tape`; add `aud`[Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape`; add `safe-publish-latest`↗️ pug-code-gen (indirect, 2.0.2 → 3.0.3) · Repo · Changelog
Security Advisories 🚨
🚨 Pug allows JavaScript code execution if an application accepts untrusted input
🚨 Remote code execution via the `pretty` option.
🚨 Remote code execution via the `pretty` option.
↗️ pug-walk (indirect, 1.1.8 → 2.0.0) · Repo · Changelog
↗️ to-fast-properties (indirect, 1.0.3 → 2.0.0) · Repo
Commits
See the full diff on Github. The new version differs by 4 commits:
2.0.0Meta tweaksAvoid throw away functions and eval trickery (#8)ES2015ify and require Node.js 4🆕 @babel/helper-string-parser (added, 7.24.6)
🆕 @babel/helper-validator-identifier (added, 7.24.6)
🆕 @babel/types (added, 7.24.6)
🆕 assert-never (added, 1.2.1)
🆕 babel-walk (added, 3.0.0-canary-5)
🆕 call-bind (added, 1.0.7)
🆕 define-data-property (added, 1.1.4)
🆕 es-define-property (added, 1.0.0)
🆕 es-errors (added, 1.3.0)
🆕 get-intrinsic (added, 1.2.4)
🆕 gopd (added, 1.0.1)
🆕 has-property-descriptors (added, 1.0.2)
🆕 has-proto (added, 1.0.3)
🆕 has-symbols (added, 1.0.3)
🆕 has-tostringtag (added, 1.0.2)
🆕 hasown (added, 2.0.2)
🆕 set-function-length (added, 1.2.2)
🗑️ @types/babel-types (removed)
🗑️ @types/babylon (removed)
🗑️ acorn-globals (removed)
🗑️ align-text (removed)
🗑️ babel-runtime (removed)
🗑️ babel-types (removed)
🗑️ babylon (removed)
🗑️ camelcase (removed)
🗑️ center-align (removed)
🗑️ clean-css (removed)
🗑️ cliui (removed)
🗑️ core-js (removed)
🗑️ has (removed)
🗑️ is-buffer (removed)
🗑️ kind-of (removed)
🗑️ lazy-cache (removed)
🗑️ longest (removed)
🗑️ regenerator-runtime (removed)
🗑️ repeat-string (removed)
🗑️ right-align (removed)
🗑️ uglify-js (removed)
🗑️ uglify-to-browserify (removed)
🗑️ window-size (removed)
🗑️ wordwrap (removed)
🗑️ yargs (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