CVE-2020-23311

CVE-2020-23311 is a high-severity vulnerability in Jerryscript with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-617.

Key facts

Description

There is an Assertion 'context_p->token.type == LEXER_RIGHT_BRACE || context_p->token.type == LEXER_ASSIGN || context_p->token.type == LEXER_COMMA' failed at js-parser-expr.c:3230 in parser_parse_object_initializer in JerryScript 2.2.0.

Frequently asked questions

What is CVE-2020-23311?
There is an Assertion 'context_p->token.type == LEXER_RIGHT_BRACE || context_p->token.type == LEXER_ASSIGN || context_p->token.type == LEXER_COMMA' failed at js-parser-expr.c:3230 in parser_parse_object_initializer in JerryScript 2.2.0.
How severe is CVE-2020-23311?
CVE-2020-23311 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-23311 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (61st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-23311?
CVE-2020-23311 affects Jerryscript. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-23311?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-23311 published?
CVE-2020-23311 was published on 2021-06-10 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Jerryscript

All CVEs affecting Jerryscript →

Other CWE-617 (Reachable Assertion) vulnerabilities

Browse all CWE-617 (Reachable Assertion) vulnerabilities →