Up to [cvs.NetBSD.org] / pkgsrc / textproc / ruby-sanitize
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
textproc/ruby-sanitize: update to 6.1.3 6.1.2 (2024-07-27) Bug Fixes * The CSS URL protocol allowlist is now properly enforced in CSS Images Module Level 4 image and image-set functions. @ltk - #240 6.1.3 (2024-08-14) Bug Fixes * The CSS URL protocol allowlist is now enforced on the nonstandard -webkit-image-set CSS function. @ltk - #242
textproc/ruby-sanitize: update to 6.1.2 6.1.2 (2024-07-27) Bug Fixes * The CSS URL protocol allowlist is now properly enforced in CSS Images Module Level 4 image and image-set functions. @ltk - #240
textproc/ruby-sanitize: update to 6.1.1 6.1.1 (2024-06-13) * Proactively fixed a compatibility issue with libxml >= 2.13.0 (which will be used in an upcoming version of Nokogiri) that caused HTML doctype sanitization to fail. @flavorjones - #238
textproc/ruby-sanitize: update to 6.1.0 6.1.0 (2023-09-14) Features * Added the text-decoration-skip-ink and text-decoration-thickness CSS properties to the relaxed config. @martineriksson - #228
Pullup ticket #6781 - requested by taca
textproc/ruby-sanitize: security fix (CVE-2023-36823)
Revisions pulled up:
- textproc/ruby-sanitize/Makefile 1.3
- textproc/ruby-sanitize/distinfo 1.3
---
Module Name: pkgsrc
Committed By: taca
Date: Sun Jul 9 02:56:28 UTC 2023
Modified Files:
pkgsrc/textproc/ruby-sanitize: Makefile distinfo
Log Message:
textproc/ruby-sanitize: update to 6.0.2
6.0.2 (2023-07-06)
Bug Fixes
* CVE-2023-36823: Fixed an HTML+CSS sanitization bypass that could allow XSS
(cross-site scripting). This issue affects Sanitize versions 3.0.0 through
6.0.1.
When using Sanitize's relaxed config or a custom config that allows
<style> elements and one or more CSS at-rules, carefully crafted input
could be used to sneak arbitrary HTML through Sanitize.
See the following security advisory for additional details:
GHSA-f5ww-cq3m-q3g7
Thanks to @cure53 for finding this issue.
textproc/ruby-sanitize: update to 6.0.2 6.0.2 (2023-07-06) Bug Fixes * CVE-2023-36823: Fixed an HTML+CSS sanitization bypass that could allow XSS (cross-site scripting). This issue affects Sanitize versions 3.0.0 through 6.0.1. When using Sanitize's relaxed config or a custom config that allows <style> elements and one or more CSS at-rules, carefully crafted input could be used to sneak arbitrary HTML through Sanitize. See the following security advisory for additional details: GHSA-f5ww-cq3m-q3g7 Thanks to @cure53 for finding this issue.
textproc/ruby-sanitize: update to 6.0.1 6.0.1 (2023-01-27) Bug Fixes * Sanitize now always removes <noscript> elements and their contents, even when noscript is in the allowlist. This fixes a sanitization bypass that could occur when noscript was allowed by a custom allowlist. In this scenario, carefully crafted input could sneak arbitrary HTML through Sanitize, potentially enabling an XSS (cross-site scripting) attack. Sanitize's default configs don't allow <noscript> elements and are not vulnerable. This issue only affects users who are using a custom config that adds noscript to the element allowlist. The root cause of this issue is that HTML parsing rules treat the contents of a <noscript> element differently depending on whether scripting is enabled in the user agent. Nokogiri doesn't support scripting so it follows the "scripting disabled" rules, but a web browser with scripting enabled will follow the "scripting enabled" rules. This means that Sanitize can't reliably make the contents of a <noscript> element safe for scripting enabled browsers, so the safest thing to do is to remove the element and its contents entirely. See the following security advisory for additional details: GHSA-fw3g-2h3j-qmm7 Thanks to David Klein from TU Braunschweig (@leeN) for reporting this issue. * Fixed an edge case in which the contents of an "unescaped text" element (such as <noembed> or <xmp>) were not properly escaped if that element was allowlisted and was also inside an allowlisted <math> or <svg> element. The only way to encounter this situation was to ignore multiple warnings in the readme and create a custom config that allowlisted all the elements involved, including <math> or <svg>. If you're using a default config or if you heeded the warnings about MathML and SVG not being supported, you're not affected by this issue. Please let this be a reminder that Sanitize cannot safely sanitize MathML or SVG content and does not support this use case. The default configs don't allow MathML or SVG elements, and allowlisting MathML or SVG elements in a custom config may create a security vulnerability in your application. Documentation has been updated to add more warnings and to make the existing warnings about this more prominent. Thanks to David Klein from TU Braunschweig (@leeN) for reporting this issue.
textproc/ruby-sanitize: add package version 6.0.0 It is required for forthcoming redmine50 package. Sanitize is an allowlist-based HTML and CSS sanitizer. It removes all HTML and/or CSS from a string except the elements, attributes, and properties you choose to allow.