ruby-sanitize - Debian Package Tracker

general

source: ruby-sanitize (main)
version: 6.0.0-1.1
maintainer: Debian Ruby Team (archive) (DMD)
uploaders: Jonas Genannt [DMD]
arch: all
std-ver: 4.6.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 4.6.6-2.1~deb10u1
o-o-sec: 4.6.6-2.1~deb10u1
oldstable: 5.2.1-2
old-bpo: 6.0.0-1~bpo11+1
stable: 6.0.0-1.1
unstable: 6.0.0-1.1

versioned links

4.6.6-2.1~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.2.1-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
6.0.0-1~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
6.0.0-1.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

ruby-sanitize

action needed

A new upstream version is available: 6.1.0 high

A new upstream version 6.1.0 is available, you should consider packaging it.

Created: 2023-01-31 Last update: 2023-10-08 02:41

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2022-09-28 Last update: 2023-10-03 20:37

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2023-36823: Sanitize is an allowlist-based HTML and CSS sanitizer. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize starting with version 3.0.0 and prior to version 6.0.2 when Sanitize is configured to use the built-in "relaxed" config or when using a custom config that allows `style` elements and one or more CSS at-rules. This could result in cross-site scripting or other undesired behavior when the malicious HTML and CSS are rendered in a browser. Sanitize 6.0.2 performs additional escaping of CSS in `style` element content, which fixes this issue. Users who are unable to upgrade can prevent this issue by using a Sanitize config that doesn't allow `style` elements, using a Sanitize config that doesn't allow CSS at-rules, or by manually escaping the character sequence `</` as `<\/` in `style` element content.

Created: 2023-07-06 Last update: 2023-09-27 19:01

2 security issues in buster high

There are 2 open security issues in buster.

1 important issue:

CVE-2023-36823: Sanitize is an allowlist-based HTML and CSS sanitizer. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize starting with version 3.0.0 and prior to version 6.0.2 when Sanitize is configured to use the built-in "relaxed" config or when using a custom config that allows `style` elements and one or more CSS at-rules. This could result in cross-site scripting or other undesired behavior when the malicious HTML and CSS are rendered in a browser. Sanitize 6.0.2 performs additional escaping of CSS in `style` element content, which fixes this issue. Users who are unable to upgrade can prevent this issue by using a Sanitize config that doesn't allow `style` elements, using a Sanitize config that doesn't allow CSS at-rules, or by manually escaping the character sequence `</` as `<\/` in `style` element content.

1 issue postponed or untriaged:

CVE-2023-23627: (needs triaging) Sanitize is an allowlist-based HTML and CSS sanitizer. Versions 5.0.0 and later, prior to 6.0.1, are vulnerable to Cross-site Scripting. When Sanitize is configured with a custom allowlist that allows `noscript` elements, attackers are able to include arbitrary HTML, resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. The default configurations do not 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. This issue has been patched in version 6.0.1. Users who are unable to upgrade can prevent this issue by using one of Sanitize's default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.

Created: 2023-07-06 Last update: 2023-09-27 19:01

2 security issues in bullseye high

There are 2 open security issues in bullseye.

1 important issue:

CVE-2023-36823: Sanitize is an allowlist-based HTML and CSS sanitizer. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize starting with version 3.0.0 and prior to version 6.0.2 when Sanitize is configured to use the built-in "relaxed" config or when using a custom config that allows `style` elements and one or more CSS at-rules. This could result in cross-site scripting or other undesired behavior when the malicious HTML and CSS are rendered in a browser. Sanitize 6.0.2 performs additional escaping of CSS in `style` element content, which fixes this issue. Users who are unable to upgrade can prevent this issue by using a Sanitize config that doesn't allow `style` elements, using a Sanitize config that doesn't allow CSS at-rules, or by manually escaping the character sequence `</` as `<\/` in `style` element content.

1 issue left for the package maintainer to handle:

CVE-2023-23627: (needs triaging) Sanitize is an allowlist-based HTML and CSS sanitizer. Versions 5.0.0 and later, prior to 6.0.1, are vulnerable to Cross-site Scripting. When Sanitize is configured with a custom allowlist that allows `noscript` elements, attackers are able to include arbitrary HTML, resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser. The default configurations do not 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. This issue has been patched in version 6.0.1. Users who are unable to upgrade can prevent this issue by using one of Sanitize's default configs or by ensuring that their custom config does not include `noscript` in the element allowlist.

You can find information about how to handle this issue in the security team's documentation.

Created: 2023-01-30 Last update: 2023-09-27 19:01

1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:

CVE-2023-36823: Sanitize is an allowlist-based HTML and CSS sanitizer. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize starting with version 3.0.0 and prior to version 6.0.2 when Sanitize is configured to use the built-in "relaxed" config or when using a custom config that allows `style` elements and one or more CSS at-rules. This could result in cross-site scripting or other undesired behavior when the malicious HTML and CSS are rendered in a browser. Sanitize 6.0.2 performs additional escaping of CSS in `style` element content, which fixes this issue. Users who are unable to upgrade can prevent this issue by using a Sanitize config that doesn't allow `style` elements, using a Sanitize config that doesn't allow CSS at-rules, or by manually escaping the character sequence `</` as `<\/` in `style` element content.

Created: 2023-07-06 Last update: 2023-09-27 19:01

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2023-36823: Sanitize is an allowlist-based HTML and CSS sanitizer. Using carefully crafted input, an attacker may be able to sneak arbitrary HTML and CSS through Sanitize starting with version 3.0.0 and prior to version 6.0.2 when Sanitize is configured to use the built-in "relaxed" config or when using a custom config that allows `style` elements and one or more CSS at-rules. This could result in cross-site scripting or other undesired behavior when the malicious HTML and CSS are rendered in a browser. Sanitize 6.0.2 performs additional escaping of CSS in `style` element content, which fixes this issue. Users who are unable to upgrade can prevent this issue by using a Sanitize config that doesn't allow `style` elements, using a Sanitize config that doesn't allow CSS at-rules, or by manually escaping the character sequence `</` as `<\/` in `style` element content.

Created: 2023-07-06 Last update: 2023-07-18 19:30

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 2-day delay is over. Check why.

Created: 2023-09-27 Last update: 2023-10-08 03:02

debian/patches: 4 patches to forward upstream low

Among the 4 debian patches available in version 6.0.0-1.1 of the package, we noticed the following issues:

4 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2023-02-26 15:54

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.2 instead of 4.6.0).

Created: 2022-05-11 Last update: 2023-02-23 07:40

testing migrations

excuses:
- Migration status for ruby-sanitize (- to 6.0.0-1.1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Updating ruby-sanitize would introduce bugs in testing: #1041430
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/ruby-sanitize.html
- ∙ ∙ autopkgtest for ruby-sanitize/6.0.0-1.1: amd64: Pass, arm64: Pass, armel: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, s390x: Pass
- ∙ ∙ Required age reduced by 3 days because of autopkgtest
- ∙ ∙ 227 days old (needed 2 days)
- Not considered

news

[rss feed]

[2023-09-28] ruby-sanitize REMOVED from testing (Debian testing watch)
[2023-03-05] ruby-sanitize 6.0.0-1.1 MIGRATED to testing (Debian testing watch)
[2023-02-22] Accepted ruby-sanitize 6.0.0-1.1 (source) into unstable (Salvatore Bonaccorso)
[2023-02-09] Accepted ruby-sanitize 6.0.0-1~bpo11+1 (source all) into bullseye-backports (Debian FTP Masters) (signed by: Utkarsh Gupta)
[2022-02-01] ruby-sanitize 6.0.0-1 MIGRATED to testing (Debian testing watch)
[2022-01-27] Accepted ruby-sanitize 6.0.0-1 (source) into unstable (Lucas Kanashiro)
[2021-11-29] ruby-sanitize 5.2.3-1 MIGRATED to testing (Debian testing watch)
[2021-11-24] Accepted ruby-sanitize 5.2.3-1 (source) into unstable (Daniel Leidert)
[2020-12-07] ruby-sanitize 5.2.1-2 MIGRATED to testing (Debian testing watch)
[2020-12-01] Accepted ruby-sanitize 5.2.1-2 (source) into unstable (Pirate Praveen) (signed by: Praveen Arimbrathodiyil)
[2020-11-12] Accepted ruby-sanitize 5.2.1-1 (source) into experimental (Pirate Praveen) (signed by: Praveen Arimbrathodiyil)
[2020-07-23] Accepted ruby-sanitize 4.6.6-2.1~deb10u1 (source) into proposed-updates->stable-new, proposed-updates (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2020-07-19] Accepted ruby-sanitize 4.6.6-2.1~deb10u1 (source) into stable->embargoed, stable (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2020-07-18] ruby-sanitize 4.6.6-2.1 MIGRATED to testing (Debian testing watch)
[2020-07-15] Accepted ruby-sanitize 4.6.6-2.1 (source) into unstable (Salvatore Bonaccorso)
[2019-02-10] ruby-sanitize 4.6.6-2 MIGRATED to testing (Debian testing watch)
[2019-02-07] Accepted ruby-sanitize 4.6.6-2 (source) into unstable (Antonio Terceiro)
[2018-12-30] Accepted ruby-sanitize 2.1.0-2+deb9u1 (source) into proposed-updates->stable-new, proposed-updates (Salvatore Bonaccorso)
[2018-12-27] Accepted ruby-sanitize 2.1.0-2+deb9u1 (source) into stable->embargoed, stable (Salvatore Bonaccorso)
[2018-08-31] Accepted ruby-sanitize 4.6.6-1~bpo9+1 (source all) into stretch-backports, stretch-backports (Pirate Praveen) (signed by: Praveen Arimbrathodiyil)
[2018-08-25] ruby-sanitize 4.6.6-1 MIGRATED to testing (Debian testing watch)
[2018-08-23] Accepted ruby-sanitize 4.6.6-1 (source) into unstable (Pirate Praveen) (signed by: Praveen Arimbrathodiyil)
[2018-06-13] Accepted ruby-sanitize 4.6.5-1 (source) into experimental (Pirate Praveen) (signed by: Praveen Arimbrathodiyil)
[2018-05-17] ruby-sanitize REMOVED from testing (Debian testing watch)
[2016-03-01] ruby-sanitize 2.1.0-2 MIGRATED to testing (Debian testing watch)
[2016-02-25] Accepted ruby-sanitize 2.1.0-2 (source all) into unstable (Balasankar C) (signed by: Praveen Arimbrathodiyil)
[2014-03-14] ruby-sanitize 2.1.0-1 MIGRATED to testing (Debian testing watch)
[2014-03-03] Accepted ruby-sanitize 2.1.0-1 (source all) (Jonas Genannt) (signed by: Cédric Boutillier)

bugs [bug history graph]

all: 1
RC: 1
I&N: 0
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian
buildd: logs
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 6.0.0-1.1