Bump loofah from 2.0.3 to 2.3.1
Created by: dependabot[bot]
Bumps loofah from 2.0.3 to 2.3.1.
Release notes
Sourced from loofah's releases.
2.3.1 / 2019-10-22
Security
Address CVE-2019-15587: Unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.
This CVE's public notice is at flavorjones/loofah#171
2.3.0 / 2019-09-28
Features
- Expand set of allowed protocols to include
tel:
andline:
. [#104, #147]- Expand set of allowed CSS functions. [related to #122]
- Allow greater precision in shorthand CSS values. #149 (Thanks, @danfstucky!)
- Allow CSS property
list-style
#162 (Thanks, @jaredbeck!)- Allow CSS keywords
thick
andthin
#168 (Thanks, @georgeclaghorn!)- Allow HTML property
contenteditable
#167 (Thanks, @andreynering!)Bug fixes
- CSS hex values are no longer limited to lowercase hex. Previously uppercase hex were scrubbed. #165 (Thanks, @asok!)
Deprecations / Name Changes
The following method and constants are hereby deprecated, and will be completely removed in a future release:
- Deprecate
Loofah::Helpers::ActionView.white_list_sanitizer
, please useLoofah::Helpers::ActionView.safe_list_sanitizer
instead.- Deprecate
Loofah::Helpers::ActionView::WhiteListSanitizer
, please useLoofah::Helpers::ActionView::SafeListSanitizer
instead.- Deprecate
Loofah::HTML5::WhiteList
, please useLoofah::HTML5::SafeList
instead.Thanks to @JuanitoFatas for submitting these changes in #164 and for making the language used in Loofah more inclusive.
v2.2.3
Notably, this release addresses CVE-2018-16468.
v2.2.2
2.2.2 / 2018-03-22
Make public
Loofah::HTML5::Scrub.force_correct_attribute_escaping!
, which was previously a private method. This is so that downstream gems (like rails-html-sanitizer) can use this logic directly for their own attribute scrubbers should they need to address CVE-2018-8048.v2.2.1
Notably, this release mitigates CVE-2018-8048.
... (truncated)
Changelog
Sourced from loofah's changelog.
2.3.1 / 2019-10-22
Security
Address CVE-2019-15587: Unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.
This CVE's public notice is at flavorjones/loofah#171
2.3.0 / 2019-09-28
Features
- Expand set of allowed protocols to include
tel:
andline:
. [#104, #147]- Expand set of allowed CSS functions. [related to #122]
- Allow greater precision in shorthand CSS values. #149 (Thanks, @danfstucky!)
- Allow CSS property
list-style
#162 (Thanks, @jaredbeck!)- Allow CSS keywords
thick
andthin
#168 (Thanks, @georgeclaghorn!)- Allow HTML property
contenteditable
#167 (Thanks, @andreynering!)Bug fixes
- CSS hex values are no longer limited to lowercase hex. Previously uppercase hex were scrubbed. #165 (Thanks, @asok!)
Deprecations / Name Changes
The following method and constants are hereby deprecated, and will be completely removed in a future release:
- Deprecate
Loofah::Helpers::ActionView.white_list_sanitizer
, please useLoofah::Helpers::ActionView.safe_list_sanitizer
instead.- Deprecate
Loofah::Helpers::ActionView::WhiteListSanitizer
, please useLoofah::Helpers::ActionView::SafeListSanitizer
instead.- Deprecate
Loofah::HTML5::WhiteList
, please useLoofah::HTML5::SafeList
instead.Thanks to @JuanitoFatas for submitting these changes in #164 and for making the language used in Loofah more inclusive.
2.2.3 / 2018-10-30
Security
Address CVE-2018-16468: Unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.
This CVE's public notice is at flavorjones/loofah#154
Meta / 2018-10-27
The mailing list is now on Google Groups #146:
... (truncated)
Commits
-
83df303
version bump to v2.3.1 -
e323a77
Merge pull request #172 from flavorjones/171-xss-vulnerability -
1d81f91
update CHANGELOG -
0c6617a
mitigate XSS vulnerability in SVG animate attributes -
a5bd819
rufo formatting -
1bdf276
formatting in README -
1908dc2
update CHANGELOG with release date -
bcbd7b3
update dev gemspec -
f6d4c2d
version bump to v2.3.0 -
08fee8c
update dev deps - Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot ignore this [patch|minor|major] version
will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.