Skip to content
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.

chore(deps): update dependency sanitize-html to >= 2.12.1 [security] - autoclosed #670

Closed
wants to merge 1 commit into from

Conversation

svc-secops
Copy link
Contributor

@svc-secops svc-secops commented Dec 19, 2023

This PR contains the following updates:

Package Change
sanitize-html [1.27.5 -> >= 2.12.1](https://renovatebot.com/diffs/npm/sanitize-html/1.27.5/>= 2.12.1)

GitHub Vulnerability Alerts

CVE-2021-26540

Apostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the "allowedIframeHostnames" option when the "allowIframeRelativeUrls" is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with "/\example.com".

CVE-2021-26539

Apostrophe Technologies sanitize-html before 2.3.1 does not properly handle internationalized domain name (IDN) which could allow an attacker to bypass hostname whitelist validation set by the "allowedIframeHostnames" option.

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.

CVE-2022-25887

The package sanitize-html before 2.7.1 are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure global regular expression replacement logic of HTML comment removal.


Configuration

📅 Schedule: Branch creation - "" in timezone Etc/UTC, Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


This PR has been generated by Renovate Bot.

@svc-secops svc-secops requested a review from a team as a code owner December 19, 2023 12:38
@svc-secops svc-secops added dependencies Pull requests that update a dependency file vulnerability labels Dec 19, 2023
@svc-secops
Copy link
Contributor Author

svc-secops commented Dec 19, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: docs@undefined
npm ERR! Found: gatsby@4.25.4
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"4.25.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^5.0.0-next" from gatsby-transformer-remark@6.13.1
npm ERR! node_modules/gatsby-transformer-remark
npm ERR!   gatsby-transformer-remark@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-05-09T12_42_36_766Z-debug-0.log

Copy link

netlify bot commented Dec 19, 2023

Deploy Preview for apollo-monodocs failed.

Name Link
🔨 Latest commit 8ab7dd4
🔍 Latest deploy log https://app.netlify.com/sites/apollo-monodocs/deploys/6676b16196ba400008902c45

@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch from 86200a0 to f075bb9 Compare December 21, 2023 13:13
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 6 times, most recently from 33b0c63 to 52e00d7 Compare January 10, 2024 13:04
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 4 times, most recently from dc631de to 8b4976d Compare January 17, 2024 13:02
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 5 times, most recently from eab6a86 to 24829f9 Compare January 26, 2024 12:55
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 4 times, most recently from 6d5cbf6 to 6a3417a Compare February 8, 2024 12:37
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 5 times, most recently from 4095f9c to 59f2508 Compare February 21, 2024 12:47
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 2 times, most recently from aa7cdc8 to e4678f5 Compare May 1, 2024 11:51
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 2 times, most recently from 628d10f to 3252d21 Compare May 9, 2024 12:42
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch from 3252d21 to fd143a3 Compare May 11, 2024 11:53
@svc-secops
Copy link
Contributor Author

svc-secops commented May 11, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: docs@undefined
npm ERR! Found: gatsby@4.25.4
npm ERR! node_modules/gatsby
npm ERR!   gatsby@"4.25.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer gatsby@"^5.0.0-next" from gatsby-transformer-remark@6.13.1
npm ERR! node_modules/gatsby-transformer-remark
npm ERR!   gatsby-transformer-remark@"^6.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-06-22T11_11_20_135Z-debug-0.log

@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 3 times, most recently from bf46991 to 1222bc1 Compare May 22, 2024 11:21
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 4 times, most recently from 391e833 to cf19429 Compare May 30, 2024 11:36
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 5 times, most recently from e00c596 to cbacbae Compare June 7, 2024 12:16
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch 5 times, most recently from 9490564 to ef78946 Compare June 14, 2024 12:46
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch from ef78946 to a4785aa Compare June 21, 2024 12:34
@svc-secops svc-secops force-pushed the renovate/npm-sanitize-html-vulnerability branch from a4785aa to 8ab7dd4 Compare June 22, 2024 11:11
@svc-secops svc-secops changed the title chore(deps): update dependency sanitize-html to 2.12.1 [security] chore(deps): update dependency sanitize-html to >= 2.12.1 [security] Jun 25, 2024
@svc-secops svc-secops changed the title chore(deps): update dependency sanitize-html to >= 2.12.1 [security] chore(deps): update dependency sanitize-html to >= 2.12.1 [security] - autoclosed Sep 12, 2024
@svc-secops svc-secops closed this Sep 12, 2024
@svc-secops svc-secops deleted the renovate/npm-sanitize-html-vulnerability branch September 12, 2024 13:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file vulnerability
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant