Service interruption via recursive CDATA sanitization
Published Dec 14, 2022 · Updated Nov 3, 2025
Uncontrolled recursion in Loofah 2.2.0 through 2.19.0 allows remote attackers to interrupt service via nested CDATA input. The strip scrubber reparses a CDATA child through Loofah.fragment and scrub!, repeating for nested script elements until Ruby exhausts its call stack and raises SystemStackError. A network-facing application must pass attacker-controlled HTML to an affected Loofah sanitizer; the exception and CPU consumption can interrupt that application.
Summary
What happened
Uncontrolled recursion in Loofah 2.2.0 through 2.19.0 allows remote attackers to interrupt service via nested CDATA input. The strip scrubber reparses a CDATA child through Loofah.fragment and scrub!, repeating for nested script elements until Ruby exhausts its call stack and raises SystemStackError. A network-facing application must pass attacker-controlled HTML to an affected Loofah sanitizer; the exception and CPU consumption can interrupt that application.
The record
- CVE
- CVE-2022-23516
- Published
- Dec 14, 2022
- Updated
- Nov 3, 2025
- Vendor
- flavorjones
- Product
- Loofah
- Classifications
- CWE-674, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.2.0, < 2.19.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo