Skip to content

🚨 [security] Update rails-html-sanitizer: 1.0.3 → 1.0.4 (patch) #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Mar 22, 2018

⚠️ No CI detected ⚠️

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

  • Our friends at Travis-CI provide excellent service.
  • Circle CI are good, too, and have a free plan that will cover basic needs.
  • If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
  • If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

It might be necessary to once deactivate and reactivate your project in Depfu for the CI service to be properly detected.




🚨 Your version of rails-html-sanitizer has known security vulnerabilities 🚨

Advisory: CVE-2018-3741
Disclosed: March 22, 2018
URL: https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae

Possible XSS vulnerability in rails-html-sanitizer

🚨 We recommend to merge and deploy this update as soon as possible! 🚨

We've updated a dependency and here is what you need to know:

name version specification old version new version
rails-html-sanitizer indirect dependency 1.0.3 1.0.4

Additionally, the update changed a few other dependencies as well:

action name old version new version
updated loofah 2.1.1 2.2.2
updated nokogiri 1.8.1 1.8.2

You should probably take a good look at the info here and the test results before merging this pull request, of course.

What changed?

↗️ rails-html-sanitizer (indirect, 1.0.3 → 1.0.4) · Repo · Changelog

Release Notes

From the Github release:

Commits

See the full diff on Github. The new version differs by 16 commits:

↗️ loofah (indirect, 2.1.1 → 2.2.2) · Repo · Changelog

Release Notes

From the Github release:

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.

Commits

See the full diff on Github. The new version differs by 47 commits:

↗️ nokogiri (indirect, 1.8.1 → 1.8.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 29 commits:


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.

Depfu Status

@depfu depfu bot added the depfu label Mar 22, 2018
@depfu
Copy link
Author

depfu bot commented Jun 30, 2022

Closed in favor of #207.

@depfu depfu bot closed this Jun 30, 2022
@depfu depfu bot deleted the depfu/update/rails-html-sanitizer-1.0.4 branch June 30, 2022 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants