Skip to content

Uncontrolled Recursion in Loofah

High severity GitHub Reviewed Published Dec 13, 2022 in flavorjones/loofah • Updated Sep 14, 2023

Package

bundler loofah (RubyGems)

Affected versions

>= 2.2.0, < 2.19.1

Patched versions

2.19.1

Description

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 who are unable to upgrade may be able to mitigate this vulnerability by limiting the length of the strings that are sanitized.

Severity

The Loofah maintainers have evaluated this as High Severity 7.5 (CVSS3.1).

References

References

@flavorjones flavorjones published to flavorjones/loofah Dec 13, 2022
Published to the GitHub Advisory Database Dec 13, 2022
Reviewed Dec 13, 2022
Published by the National Vulnerability Database Dec 14, 2022
Last updated Sep 14, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.101%
(42nd percentile)

Weaknesses

CVE ID

CVE-2022-23516

GHSA ID

GHSA-3x8r-x6xp-q4vm

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.