Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.5
CVE-2021-46343: There is an Assertion 'context_p->token.type == LEXER_LITERAL' failed at /jerry-core/parser/js/js-parser-expr.c in JerryScript 3.0.0.
CVE-2021-46343 · published 4 years ago
Summary
There is an Assertion 'context_p->token.type == LEXER_LITERAL' failed at /jerry-core/parser/js/js-parser-expr.c in JerryScript 3.0.0.
What to do
The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| jerryscript | jerryscript |
3.0.0 cpe:2.3:a:jerryscript:jerryscript:3.0.0:*:*:*:*:*:*:* |
Original advisory text
There is an Assertion 'context_p->token.type == LEXER_LITERAL' failed at /jerry-core/parser/js/js-parser-expr.c in JerryScript 3.0.0.
There is an Assertion 'context_p->token.type == LEXER_LITERAL' failed at /jerry-core/parser/js/js-parser-expr.c in JerryScript 3.0.0.
References
- https://github.com/jerryscript-project/jerryscript/issues/4921 Exploit Issue Tracking Patch Third Party Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker partial control (estimated)
Type
CWE-617Reachable Assertion
Timeline
Published20 Jan 2022
Updated4 Nov 2026
First seen29 Sep 2026
Sources
CVE-2021-46343 · NVD
Track software like this
Free during beta