loofah vulnerabilities
Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. Loofah also includes some HTML sanitizers based on `html5lib`'s safelist, which are a specific application of the general transformation functionality.
- Registry
- RubyGems
- Latest
- 2.25.3
- License
- MIT
17 known advisories
The latest version, 2.25.3, is not affected by any of them. Projects on older versions may be.
bundle update --conservative loofah # Gemfile: '>= 2.25.3'Is your project on an affected loofah?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for loofah
Loofah: SVG `<textPath>` and `<mpath>` bypass local-reference restriction
- Affected
- <2.25.3
- Fixed in
- 2.25.3
Loofah allowed_uri? treats javascript: alert(1) as safe
- Affected
- >=2.25.0 <2.25.3
- Fixed in
- 2.25.3
Loofah: CSS url() sanitization bypass via escaped parentheses
- Affected
- <2.25.3
- Fixed in
- 2.25.3
Loofah: Regular expression denial of service in the SVG local-reference check
- Affected
- <2.25.3
- Fixed in
- 2.25.3
Loofah allowed_uri? treats data:text/html as safe text/plain
- Affected
- >=2.25.2 <2.25.3
- Fixed in
- 2.25.3
Loofah: Mutation XSS in the HTML5 scrubbers through unescaped attribute values
- Affected
- >=2.21.0 <2.25.3
- Fixed in
- 2.25.3
Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons
- Affected
- >=2.25.0 <2.25.2
- Fixed in
- 2.25.2
Loofah: SVG `href` attribute bypasses local-reference restriction
- Affected
- <2.25.2
- Fixed in
- 2.25.2
Loofah `allowed_uri?` does not detect `javascript:` URIs split by named whitespace character references
- Affected
- >=2.25.0 <2.25.2
- Fixed in
- 2.25.2
Loofah has improper detection of disallowed URIs via `allowed_uri?`
- Affected
- >=2.25.0 <2.25.1
- Fixed in
- 2.25.1
Improper detection of disallowed URIs by Loofah `allowed_uri?`
- Affected
- >=2.25.0 <2.25.1
- Fixed in
- 2.25.1
Uncontrolled Recursion in Loofah
- Affected
- >=2.2.0 <2.19.1
- Fixed in
- 2.19.1
Improper neutralization of data URIs may allow XSS in Loofah
- Affected
- >=2.1.0 <2.19.1
- Fixed in
- 2.19.1
Inefficient Regular Expression Complexity in Loofah
- Affected
- <2.19.1
- Fixed in
- 2.19.1
Loofah Allows Cross-site Scripting
- Affected
- <2.3.1
- Fixed in
- 2.3.1
Loofah Cross-site Scripting vulnerability
- Affected
- <2.2.3
- Fixed in
- 2.2.3
Cross-site Scripting in loofah
- Affected
- <2.2.1
- Fixed in
- 2.2.1
Is your loofah version vulnerable?
- loofah 2.25No known advisories in 2.25.3
- loofah 2.245 advisories in 2.24.1
- loofah 2.235 advisories in 2.23.1
- loofah 2.225 advisories in 2.22.0
- loofah 2.215 advisories in 2.21.4
- loofah 2.204 advisories in 2.20.0
- loofah 1.28 advisories in 1.2.1
- loofah 1.18 advisories in 1.1.0
- loofah 1.08 advisories in 1.0.0
- loofah 0.48 advisories in 0.4.7
- loofah 0.38 advisories in 0.3.1
- loofah 0.28 advisories in 0.2.2
Which of your client projects still run an old loofah?
NPMscan reads the Gemfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.