Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1568842 - (CVE-2018-3741) CVE-2018-3741 rubygem-rails-html-sanitizer: non-whitelisted attributes are present in sanitized output when input with specially-crafted HTML fragments leading to XSS vulnerability
CVE-2018-3741 rubygem-rails-html-sanitizer: non-whitelisted attributes are pr...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180321,repor...
: Security
Depends On: 1568845 1569130 1569131 1559658 1576590 1576591
Blocks: 1568847
  Show dependency treegraph
 
Reported: 2018-04-18 06:17 EDT by Adam Mariš
Modified: 2018-05-31 14:46 EDT (History)
21 users (show)

See Also:
Fixed In Version: rubygem-rails-html-sanitizer 1.0.4
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2018-04-18 06:17:48 EDT
There is a possible XSS vulnerability in all rails-html-sanitizer gem versions below 1.0.4 for Ruby. The gem allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments, and these attributes can lead to an XSS attack on target applications. This issue is similar to CVE-2018-8048 in Loofah. All users running an affected release should either upgrade or use one of the workarounds immediately.

Upstream fix:

https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae
Comment 1 Adam Mariš 2018-04-18 06:18:19 EDT
Created rubygem-rails-html-sanitizer tracking bugs for this issue:

Affects: fedora-all [bug 1568845]

Note You need to log in before you can comment on or make changes to this bug.