Advisory

GHSA-9r5m-9576-7f6x

Details, part 2 of 2. The advisory

Details

Replace http://<app>/render with the actual template rendering endpoint. The payload is pure Liquid syntax and works regardless of the HTTP framework or endpoint structure.

Impact
An attacker who can control template content (common in CMS, email template editors, and SaaS platforms using LiquidJS) can bypass the memoryLimit protection entirely and crash the Node.js process:

  • Complete bypass of the `memoryLimit` security mechanism: The explicitly configured memory limit becomes ineffective.
  • Process crash from a single HTTP request: V8 Fatal error terminates the entire Node.js process, not just the attacking request. This is not a catchable JavaScript exception.
  • Service-wide denial of service: All in-flight requests are terminated. Manual restart or container restart policy is required to recover.
  • False sense of security: Administrators who configured memoryLimit believe their service is protected when it is not.
  • Container restart policy does not mitigate: Even with Docker restart: always or Kubernetes liveness probes, repeated crash payloads can keep the service in a perpetual restart loop. Each restart takes several seconds, during which all in-flight requests are lost and the service is unavailable.

Sources & licences