sample-appointment-reminders-node
sample-appointment-reminders-node copied to clipboard
[Security] Bump pug from 2.0.3 to 3.0.2
Bumps pug from 2.0.3 to 3.0.2.
Release notes
Sourced from pug's releases.
[email protected]
Bug Fixes
Sanitise the
prettyoption (#3314)If a malicious attacker could control the
prettyoption, it was possible for them to achieve remote code execution on the server rendering the template. All pug users should upgrade as soon as possible, see #3312 for more details.[email protected]
Bug Fixes
- Serialize Buffers to strings when storing sources for use with compileDebug: true (#3269)
[email protected]
Bug Fixes
- Update
withto resolve core-js deprecation notice (#3259)[email protected]
Bug Fixes
Sanitise the
prettyoption (#3314)If a malicious attacker could control the
prettyoption, it was possible for them to achieve remote code execution on the server rendering the template. All pug users should upgrade as soon as possible, see #3312 for more details.[email protected]
Bug Fixes
- Properly handle non-string values when rethrowing errors (#3269)
[email protected]
Breaking Changes
- Drop support for node 6 and 8 (#3243)
Bug Fixes
- wrap setting err.message with a try/catch (#2996)
[email protected]
Breaking Changes
- Drop support for node 6 and 8 (#3243)
[email protected]
Breaking Changes
- Drop support for node 6 and 8 (#3243)
New Features
... (truncated)
Commits
d4b7f60Properly handle errors originating from included files when compileDebug is e...d6f0615fix capture groups for "each" statements (#3274)73ea7cffix: keep lexer plugins inside tag interpolation (#3296)29a53c5fix: Fix pug-lexer parsed escaped interpolations incorrectly (#3299)60b1b15chore: update supported versions (#3315)991e78ffix: sanitise and escape theprettyoption (#3314)06baa52Fix TypeScript and add eachOf token definition (#3262)13e46e9chore: update with (#3259)c077df4docs: fix rolling versions linkccba7daci: publish canary release (#3257)- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by pug-bot, a new releaser for pug since your current version.
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
We've just been alerted that this update fixes a security vulnerability:
Sourced from The GitHub Security Advisory Database.
Remote code execution via the
prettyoption.Impact
If a remote attacker was able to control the
prettyoption 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
[email protected]or[email protected]or[email protected], which correctly sanitise the parameter.Workarounds
If there is no way for un-trusted input to be passed to pug as the
prettyoption, e.g. if you compile templates in advance before applying user input to them, you do not need to upgrade.References
Original report: pugjs/pug#3312
For more information
If you believe you have found other vulnerabilities, please DO NOT open an issue. Instead, you can follow the instructions in our Security Policy
Affected versions: ["< 3.0.1"]