JerryScript 2.2.0 js-parser-expr.c parser_parse_expression assertion

EntryeditHistoryDiffjsonxmlCTI
CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

A vulnerability was found in JerryScript 2.2.0. It has been classified as critical. This affects the function parser_parse_expression of the file js-parser-expr.c. CWE is classifying the issue as CWE-617. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

There is an Assertion 'context_p->stack_top_uint8 == LEXER_EXPRESSION_START' at js-parser-expr.c:3565 in parser_parse_expression in JerryScript 2.2.0.

The weakness was disclosed 06/11/2021. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2020-23308 since 08/13/2020. Access to the local network is required for this attack to succeed. Required for exploitation is a authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/13/2021).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Productinfoedit

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfoedit

Class: Unknown
CWE: CWE-617
ATT&CK: Unknown

Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfoedit

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfoedit

08/13/2020 CVE assigned
06/11/2021 +302 days Advisory disclosed
06/11/2021 +0 days VulDB entry created
06/13/2021 +2 days VulDB last update

Sourcesinfoedit

Advisory: github.com
Status: Confirmed
Confirmation: 🔒

CVE: CVE-2020-23308 (🔒)

Entryinfoedit

Created: 06/11/2021 01:44 PM
Updated: 06/13/2021 02:27 PM
Changes: (3) source_cve_assigned source_cve_nvd_summary advisory_confirm_url
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Interested in the pricing of exploits?

See the underground prices here!