🚨 [security] Update bootstrap-sass 3.3.7 → 3.4.3 (minor)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this 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?

✳️ bootstrap-sass (3.3.7 → 3.4.3) · Repo · Changelog

Security Advisories 🚨

🚨 Bootstrap Vulnerable to Cross-Site Scripting

Versions of bootstrap prior to 3.4.1 for 3.x and 4.3.1 for 4.x are vulnerable to Cross-Site Scripting (XSS). The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.

Recommendation

For bootstrap 4.x upgrade to 4.3.1 or later.
For bootstrap 3.x upgrade to 3.4.1 or later.

🚨 bootstrap Cross-site Scripting vulnerability

In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property.

🚨 XSS vulnerability that affects bootstrap

In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute.

🚨 Bootstrap Cross-site Scripting vulnerability

In Bootstrap 2.x from 2.0.4, 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute. Note that this is a different vulnerability than CVE-2018-14041.

See https://blog.getbootstrap.com/2018/12/13/bootstrap-3-4-0/ for more info.

🚨 Bootstrap Cross-site Scripting vulnerability

In Bootstrap starting in version 2.3.0 and prior to versions 3.4.0 and 4.1.2, XSS is possible in the data-container property of tooltip. This is similar to CVE-2018-14041.

Release Notes

3.4.3 (from changelog)

• Fix malformed math.div expressions. #1225

3.4.2 (from changelog)

• Compatibility with Sass 1.33. #1221

3.4.0

• New: Added a .row-no-gutters class.
• New: Added docs searching via Algolia.
• Fixed: Resolved an XSS issue in Alert, Carousel, Collapse, Dropdown, Modal, and Tab components. See https://snyk.io/vuln/npm:bootstrap:20160627 for details.
• Fixed: Added padding to .navbar-fixed-* on modal open
• Fixed: Removed the double border on elements.
• Removed Gist creation in web-based Customizer since anonymous gists were disabled long ago by GitHub.
• Removed drag and drop support from Customizer since it didn’t work anymore.

Framework version: Bootstrap v3.4.0
See the upstream blog post for a detailed overview.

Does any of this look wrong? Please let us know.

Commits

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

• Bump to 3.4.3 (npm only)
• rake convert[v3.4.1]
• replace_division: balance parens
• Bump to 3.4.2 (npm only)
• package.json: node-sass -> sass
• rake convert[v3.4.1]
• handle math.div
• Rakefile: require 'bundler/gem_tasks'
• Bump bootstrap-sass to 3.4.1
• rake convert[v3.4.1]
• v3.4.0
• Revert relative imports change
• Test Rails app: Depend on sassc-rails
• rake convert[v3.4.0]
• less_conversion.rb: Update stylelint comment removal
• Remove compass support
• lotus -> hanami
• sass -> sassc
• rake convert[v3.4.0-dev]
• Fix test/node_sass_compile_test.sh
• Stop testing with sass-head and rails-head
• travis
• Fix "$a-$b" -> "#{$a}-#{$b}" conversion
• rake convert[v3.4.0-dev]
• Update converter to support v3.4.0
• Fix test/compass_test.rb for recent bundler
• Update package.json devDependencies
• readme [ci skip]
• Merge pull request #1168 from coliff/patch-1
• HTTPS relevant links
• Merge pull request #1145 from zhublik/readme
• Update bootstrap-sass version in README.
• Merge pull request #1141 from ltfschoen/patch-1
• Update README.md advising use of jquery-rails

---

👉 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:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * 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/`.

---

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

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)