CVE-2019-15587
rubygem-loofah: XXS when a crafted SVG element is republished
Overview
Description
In the Loofah gem for Ruby through v2.3.0 unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.
Source: OX vulnerability database
Severity
5.4 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Weakness: CWE-79
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| RubyGems | loofah | <2.3.1 | 2.3.1 |
Open a package to see all its vulnerabilities.
Operating systems · 16 fixes
Red Hat 2 releases · 1 package
wont fix 2
cfme-amazon-smartstate
| Release | Package | Fixed in |
|---|---|---|
| 7 | cfme-amazon-smartstate +3 | wont fix |
| 8 | cfme-amazon-smartstate +1 | wont fix |
SUSE Linux Enterprise 1 release · 1 package
fixed 1
ruby2-5-rubygem-loofah
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 15.4 | ruby2-5-rubygem-loofah | 2.2.2-150000.4.6.1 | SUSE-SU-2022:3868-1 |
debian 6 releases · 1 package
fixed 6
ruby-loofah
| Release | Package | Fixed in |
|---|---|---|
| 10 | ruby-loofah | 2.2.3-1+deb10u1 |
| 11 | ruby-loofah | 2.3.1+dfsg-1 |
| 12 | ruby-loofah | 2.3.1+dfsg-1 |
| 13 | ruby-loofah | 2.3.1+dfsg-1 |
| 14 | ruby-loofah | 2.3.1+dfsg-1 |
| 9 | ruby-loofah | 2.0.3-2+deb9u3 |
echo 1 release · 1 package
fixed 1
ruby-loofah
| Release | Package | Fixed in |
|---|---|---|
| ruby-loofah | 2.3.1+dfsg-1 |
openSUSE 1 release · 6 packages
fixed 6
ruby2-7-rubygem-loofah
ruby3-1-rubygem-loofah
ruby3-2-rubygem-loofah
ruby3-3-rubygem-loofah
ruby3-4-rubygem-loofah
ruby4-0-rubygem-loofah
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | ruby2-7-rubygem-loofah +1 | 2.12.0-1.2 | openSUSE-SU-2024:11337-1 |
| Tumbleweed | ruby3-1-rubygem-loofah | 2.14.0-1.1 | openSUSE-SU-2024:11900-1 |
| Tumbleweed | ruby3-2-rubygem-loofah | 2.19.1-1.2 | openSUSE-SU-2024:13162-1 |
| Tumbleweed | ruby3-3-rubygem-loofah | 2.22.0-1.5 | openSUSE-SU-2024:14171-1 |
| Tumbleweed | ruby3-4-rubygem-loofah | 2.23.1-1.3 | openSUSE-SU-2025:15120-1 |
| Tumbleweed | ruby4-0-rubygem-loofah | 2.23.1-1.5 | openSUSE-SU-2026:10353-1 |
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2019-15587
- github.com https://github.com/flavorjones/loofah
- github.com https://github.com/flavorjones/loofah/commit/0c6617af440879ce97440f6eb6c58636456dc8ec
- github.com https://github.com/flavorjones/loofah/issues/171
- github.com https://github.com/rubysec/ruby-advisory-db/blob/master/gems/loofah/CVE-2019-15587.yml
- hackerone.com https://hackerone.com/reports/709009
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4WK2UG7ORKRQOJ6E4XJ2NVIHYJES6BYZ/
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XMCWPLYPNIWYAY443IZZJ4IHBBLIHBP5/
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4WK2UG7ORKRQOJ6E4XJ2NVIHYJES6BYZ
- lists.fedoraproject.org https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XMCWPLYPNIWYAY443IZZJ4IHBBLIHBP5
Show all 18 references
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2019-15587
- security.netapp.com https://security.netapp.com/advisory/ntap-20191122-0003
- security.netapp.com https://security.netapp.com/advisory/ntap-20191122-0003/
- ubuntu.com https://ubuntu.com/security/notices/USN-4498-1
- usn.ubuntu.com https://usn.ubuntu.com/4498-1
- usn.ubuntu.com https://usn.ubuntu.com/4498-1/
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2019-15587
- www.debian.org https://www.debian.org/security/2019/dsa-4554
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.