Add CVE-2019-8331 for twitter-bootstrap-rails
#720
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
postmodern
approved these changes
Nov 23, 2023
postmodern
requested changes
Nov 23, 2023
postmodern
approved these changes
Nov 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CVE-2019-8331 has already been reported for the
bootstrapandbootstrap-sassgems, but thetwitter-bootstrap-railsgem is still affected, since it includes the vulnerable 3.3.6 version.I'm not sure if it's appropriate for me to tell users that "hey, there's this other version of the bootstrap gem that's actually maintained by the original developer, and until this gem is fixed you should use it instead". I have done it anyway; please let me know if that needs to be changed.