🚨 [security] Update pug 2.0.4 → 3.0.3 (major)

[depfu]

---

🚨 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

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.

🚨 Remote code execution via the `pretty` option.

Impact

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.

References

Original report: #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

✳️ chart.js (2.9.1 → 2.9.4) · Repo

Security Advisories 🚨

🚨 Prototype pollution in chart.js

This affects the package chart.js before 2.9.4. The options parameter is not properly sanitized when it is processed. When the options are processed, the existing options (or the defaults options) are deeply merged with provided options. However, during this operation, the keys of the object being set are not checked, leading to a prototype pollution.

Release Notes

2.9.4

This is the last release of v2 and focused on fixing bugs identified in the v2.9.3 release.

Bugs Fixed

• #7404 - Preserve prototypes when cloning. Thanks @iddings
• #7587 - Fix docs for external moment.js. Thanks @mojoaxel
• #7853 - Fix box recursion when dimensions are NaN. Thanks @alessandroasm
• #7883 - Fix call stack exception when computing label sizes. Thanks @silentmatt
• #7918 - Prevent global prototype pollution via the merge helper
• #7920 - Use Object.create(null) as merge target, to prevent prototype pollution

2.9.3

Bug Fixes

• #6698 Fix undefined variable
• #6719 Don't make legend empty when fill is false

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@kurkle, @benmccann, and @etimberg).

2.9.2

Bug Fixes

• #6641 IE11 & Edge compatible style injection
• #6655 Backwards compatible default fill for radar charts
• #6660 Improve clipping of line charts when border widths are large
• #6661 When a legend item is clicked, make sure the correct item is hidden
• #6663 Refresh package-lock file to pick up new dependency

Performance

• #6671 Stop unnecessary line calculations

Documentation

• #6643 Combine performance documentation sections

Thanks to the maintainers and collaborators for their help to improve and test Chart.js (@nagix, @kurkle, @benmccann, @etimberg and @simonbrunel).

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ acorn (indirect, 3.3.0 → 7.4.1) · Repo

Security Advisories 🚨

🚨 Regular Expression Denial of Service in Acorn

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.

🚨 Regular Expression Denial of Service in Acorn

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.

🚨 Regular Expression Denial of Service in Acorn

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.

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.1
• Release 4.0.0
• chore: 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

↗️ 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

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.

🚨 Remote code execution via the `pretty` option.

Impact

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.

References

Original report: #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

🚨 Remote code execution via the `pretty` option.

Impact

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.

References

Original report: #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

↗️ 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.0
• Meta tweaks
• Avoid 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)

🆕 assert-never (added, 1.2.1)

🆕 babel-walk (added, 3.0.0-canary-5)

🆕 hasown (added, 2.0.2)

🆕 is-core-module (added, 2.13.1)

🆕 supports-preserve-symlinks-flag (added, 1.0.0)

🗑️ @​types/babel-types (removed)

🗑️ @​types/babylon (removed)

🗑️ acorn-globals (removed)

🗑️ align-text (removed)

🗑️ babel-runtime (removed)

🗑️ babel-types (removed)

🗑️ babylon (removed)

🗑️ center-align (removed)

🗑️ clean-css (removed)

🗑️ core-js (removed)

🗑️ emoji-regex (removed)

🗑️ kind-of (removed)

🗑️ lazy-cache (removed)

🗑️ longest (removed)

🗑️ regenerator-runtime (removed)

🗑️ repeat-string (removed)

🗑️ right-align (removed)

🗑️ uglify-to-browserify (removed)

🗑️ window-size (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

@​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)