Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

GHSA-MF2J-8F84-CC9Q

Regular expression denial of service in Loofah's SVG local-reference check

Overview

Published
No date
Modified
No date
Medium GitHub advisory
1 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available
CVSS score Medium, no score

Description

Summary

Loofah's HTML5 sanitizer restricts the href and xlink:href attributes of SVG reference elements to local references. That check matched the attribute value against /^\s*[^#\s].*/m. In Ruby ^ anchors to every line start and \s matches newlines, so an all-whitespace value made the engine rescan the value from each of its line starts, taking time quadratic in its length.

CRuby 3.1 and earlier, and JRuby, are affected. CRuby 3.2 added linear-time regexp matching, which makes the pattern linear. JRuby's regexp engine does not.

Impact

An attacker who supplies HTML to be sanitized can consume CPU out of proportion to the input size, by sending an SVG reference element whose href or xlink:href is a long run of whitespace.

The default safelist allows the elements in SVG_ALLOW_LOCAL_HREF, so no configuration change is required.

Mitigation

Upgrade to Loofah >= 2.25.3. Applications on CRuby that cannot upgrade should run CRuby 3.2 or later, which matches the pattern in linear time.

References

Credit

Reported by scyoon through the Rails HackerOne program.

Source: OX vulnerability database

Severity

MEDIUM

No CVSS vector in the source. Severity comes from the advisory.

Affected packages · 1

Packages affected by GHSA-MF2J-8F84-CC9Q
EcosystemPackageVulnerableFixed in
RubyGems loofah — 2.25.3

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

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.