This repository was archived by the owner on Jun 6, 2020. It is now read-only.
🚨 [security] Update loofah: 2.2.2 → 2.3.1 (minor) #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Your version of loofah has known security vulnerabilities 🚨
Advisory: CVE-2019-15587
Disclosed: October 22, 2019
URL: https://github.com/flavorjones/loofah/issues/171
Loofah XSS Vulnerability
🚨 We recommend to merge and deploy this update as soon as possible! 🚨
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
Release Notes
2.3.1
2.3.0 (from changelog)
2.2.3
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 48 commits:
version bump to v2.3.1Merge pull request #172 from flavorjones/171-xss-vulnerabilityupdate CHANGELOGmitigate XSS vulnerability in SVG animate attributesrufo formattingformatting in READMEupdate CHANGELOG with release dateupdate dev gemspecversion bump to v2.3.0update dev depsupdate README to work with modern Hoeupdate ManifestMerge branch 'jf.safelist'formatting CHANGELOGOnly call deprecate_constant if availableUse safelist consistentlyUse safelist(s), allowlist(s) where applicableupdate CHANGELOGci: remove unused code from rake-test/run.shMerge pull request #167 from jobscore/allow-html-property-contenteditableMerge pull request #168 from georgeclaghorn/border-width-keyword-valuesAllow the thin and thick CSS keywordsAllow HTML property: contenteditableupdate to latest concourse-gemupdate dev dependencieschangelog: update for #162Merge pull request #162 from jaredbeck/allow_list-stylechangelog: update for #165Merge pull request #165 from asok/correct-css-keywordish-regexpFix test for style attribute scrubbingAdd a test for testing style attribute scrubbingCorrect the regexp for kewordish css property which hold a hex valueAllow CSS property `list-style`cherry-pick v2.2.3 changelog entryremove the svg animate attribute `from` from the allowlistremove versioneye from readmeMerge branch 'flavorjones-allowlist-changes'update CHANGELOGAllow greater precision in values of shorthand css elementsfailing test for high-precision CSS valuesupdate CHANGELOGexpand allowed protocols to allow `tel:` and `line:`expand set of allowed CSS functionsreformat `whitelist.rb`scripts to inspect and compare DOMPurify metadataadd formatting to CHANGELOGupdated mailing list to a new Google Groupextract msword html data into an asset fileRelease Notes
1.0.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
Release 1.0.5Remove test files and omit themRemove 1.9.3 from the test matrixUpdate Travis test matrixCommits
See the full diff on Github. The new version differs by 10 commits:
version bump to v2.4.0update CHANGELOG in preparation for v2.4.0update dev dependenciesMerge pull request #86 from eagletmt/skip-progress-when-chunkedMerge pull request #87 from halfbyte/patch-1Make version in changelog fit release version.Skip progress report when Content-Length is unavailableupdate test:examples to libiconv 1.15concourse: test most-recent two rubiesconvert to using windows-ruby-dev-tools-releaseRelease Notes
1.10.4
1.10.3
1.10.2
1.10.1
1.10.0
1.9.1
1.9.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands