Engine crash via unbounded expression recursion
Published May 28, 2021 · Updated Aug 4, 2024
Stack overflow in parse_comparison in Cesanta mJS 1.20.1 allows attackers to crash the JavaScript engine with a crafted file. Nested array literals repeatedly drive the expression-parser chain through parse_comparison without a depth limit until the process stack is exhausted. The target must parse the supplied JavaScript input; stack exhaustion terminates the engine process without reported data exposure or modification.
Summary
What happened
Stack overflow in parse_comparison in Cesanta mJS 1.20.1 allows attackers to crash the JavaScript engine with a crafted file. Nested array literals repeatedly drive the expression-parser chain through parse_comparison without a depth limit until the process stack is exhausted. The target must parse the supplied JavaScript input; stack exhaustion terminates the engine process without reported data exposure or modification.
The record
- CVE
- CVE-2020-36374
- Published
- May 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-674, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- POC.zip for mJS recursive parser stack overflowproof of concept · demonstrated
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