Summary Loofah < 2.19.1 contains an inefficient regular expression that is susceptible to excessive backtracking when attempting to sanitize certain SVG attributes. This may lead to a denial of service through CPU resource consumption. Mitigation Upgrade to Loofah >= 2.19.1. Seve...
Product
debian/ruby-loofah vulnerabilities
6 published CVES affecting debian/ruby-loofah, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 2
- Medium
- 4
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest debian/ruby-loofah CVEs
Newest publication first
-
HighCVSS 7.5 PoC
-
HighCVSS 7.5 PoC
Summary Loofah >= 2.2.0, < 2.19.1 uses recursion for sanitizing CDATA sections, making it susceptible to stack exhaustion and raising a SystemStackError exception. This may lead to a denial of service through CPU resource consumption. Mitigation Upgrade to Loofah >= 2.19.1. Users...
-
MediumCVSS 6.1 PoC
Summary Loofah >= 2.1.0, < 2.19.1 is vulnerable to cross-site scripting via the image/svg+xml media type in data URIs. Mitigation Upgrade to Loofah >= 2.19.1. Severity The Loofah maintainers have evaluated this as Medium Severity 6.1. References CWE - CWE-79: Improper Neutralizat...
-
MediumCVSS 5.4 EPSS 0.92%
In the Loofah gem for Ruby, through v2.2.2, unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.
-
MediumCVSS 6.1 PoC
In the Loofah gem through 2.2.0 for Ruby, non-whitelisted HTML attributes may occur in sanitized output by republishing a crafted HTML fragment.
-
MediumCVSS 5.4 PoC
In the Loofah gem for Ruby through v2.3.0, unsanitized JavaScript may occur in sanitized output when a crafted SVG element is republished.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.