LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| harttle | liquidjs | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Harttle | Liquidjs |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8xx9-69p8-7jp3 | LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.385% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Harttle
Harttle liquidjs |
|
| Vendors & Products |
Harttle
Harttle liquidjs |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LiquidJS is a Shopify/GitHub Pages compatible template engine written in pure JavaScript. In versions 10.25.7 and below, the renderLimit option can be fully bypassed by a {% for %} (or {% tablerow %}) tag whose body is empty. The renderLimit option is documented in docs/source/tutorials/dos.md as the mechanism that "mitigates this by limiting the time consumed by each render() call." The per-iteration time check is reached only when the body contains at least one template node, so a template such as {%- for i in (1..N) -%}{%- endfor -%} iterates the full collection without ever consulting renderLimit. With a configured renderLimit of 50 ms, a single parseAndRenderSync call has been observed to consume 2.26 seconds (~45× over the limit) and scales linearly with N up to memoryLimit, allowing a low-privileged template author to wedge an event-loop thread for an attacker-chosen duration. Deployments that rely on a finite renderLimit for DoS protection (common in multi-tenant template-authoring environments) can still be forced by a single crafted template to monopolize a Node.js event-loop worker for attacker-controlled time, potentially stalling in-flight requests, with availability impact only. This issue has been fixed in version 10.26.0. | |
| Title | LiquidJS has a renderLimit DoS guard bypass via empty `{% for %}` body | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV3_1
|