Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency sanitize-html to v2.12.1 [security] #6621

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 4, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sanitize-html 2.10.0 -> 2.12.1 age adoption passing confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2024-21501

Versions of the package sanitize-html before 2.12.1 are vulnerable to Information Exposure when used on the backend and with the style attribute allowed, allowing enumeration of files in the system (including project dependencies). An attacker could exploit this vulnerability to gather details about the file system structure and dependencies of the targeted server.


Release Notes

apostrophecms/sanitize-html (sanitize-html)

v2.12.1

Compare Source

  • Do not parse sourcemaps in post-css. This fixes a vulnerability in which information about the existence or non-existence of files on a server could be disclosed via properly crafted HTML input when the style attribute is allowed by the configuration. Thanks to the Snyk Security team for the disclosure and to Dylan Armstrong for the fix.

v2.12.0

Compare Source

  • Introduced the allowedEmptyAttributes option, enabling explicit specification of empty string values for select attributes, with the default attribute set to alt. Thanks to Na for the contribution.

  • Clarified the use of SVGs with a new test and changes to documentation. Thanks to Gauav Kumar for the contribution.

  • Do not process source maps when processing style tags with PostCSS.

v2.11.0

Compare Source

  • Fix to allow false in allowedClasses attributes. Thanks to Kevin Jiang for this fix!
  • Upgrade mocha version
  • Apply small linter fixes in tests
  • Add .idea temp files to .gitignore
  • Thanks to Vitalii Shpital for the updates!
  • Show parseStyleAttributes warning in browser only. Thanks to mog422 for this update!
  • Remove empty non-boolean attributes via an exhaustive, configurable list of known non-boolean attributes. Thanks to Dylan Armstrong for this update!

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Copy link

github-actions bot commented Oct 4, 2024

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Your PR title is: fix(deps): update dependency sanitize-html to v2.12.1 [security]
It should be something like: feat(scope): Add fancy new feature

Details:

Unknown scope "deps" found in pull request title "fix(deps): update dependency sanitize-html to v2.12.1 [security]". Scope must match one of: root, api, dashboard, inbound-mail, web, webhook, widget, worker, ws, ee-auth, ee-billing, ee-dal, ee-shared-services, ee-translation, application-generic, automation, dal, design-system, embed, novui, testing, client, framework, headless, js, nest, nextjs, node, notification-center, novu, providers, react, react-native, shared, stateless, nestjs, nextjs.

Copy link

netlify bot commented Oct 4, 2024

Deploy Preview for novu-stg-vite-dashboard-poc failed. Why did it fail? →

Name Link
🔨 Latest commit 32af262
🔍 Latest deploy log https://app.netlify.com/sites/novu-stg-vite-dashboard-poc/deploys/6722b2161efaa20008973eab

@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from a3f1d19 to 4651570 Compare October 4, 2024 14:09
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 4651570 to f8f7d24 Compare October 4, 2024 14:46
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from f8f7d24 to a382523 Compare October 4, 2024 15:09
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from a382523 to 0c1652f Compare October 4, 2024 17:03
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 0c1652f to ce12963 Compare October 4, 2024 19:01
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from ce12963 to 999b230 Compare October 4, 2024 19:42
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 999b230 to 6cf09d1 Compare October 6, 2024 13:08
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 87b71a6 to 13eb00d Compare October 29, 2024 16:12
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 13eb00d to a2163ab Compare October 29, 2024 17:13
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from a2163ab to 6038ce4 Compare October 30, 2024 08:56
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 6038ce4 to 34858c2 Compare October 30, 2024 10:00
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from 34858c2 to d795c3c Compare October 30, 2024 13:36
@renovate renovate bot force-pushed the renovate/npm-sanitize-html-vulnerability branch from d795c3c to 6cabc0d Compare October 30, 2024 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants