VDB-228925 · CVE-2023-31920 · Issue 5070

Jerryscript 3.0 jerry-core/vm/vm.c vm_loop assertion

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-$5k	0.00

Summaryinfo

A vulnerability marked as critical has been reported in Jerryscript 3.0. This issue affects the function vm_loop of the file jerry-core/vm/vm.c. This manipulation causes assertion. This vulnerability is registered as CVE-2023-31920. No exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Jerryscript 3.0. Affected by this vulnerability is the function vm_loop of the file jerry-core/vm/vm.c. The manipulation with an unknown input leads to a assertion vulnerability. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. The impact remains unknown. The summary by CVE is:

Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the vm_loop at jerry-core/vm/vm.c.

The weakness was published 05/12/2023 as 5070. The advisory is shared at github.com. This vulnerability is known as CVE-2023-31920 since 04/29/2023. Technical details are known, but no exploit is available.

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

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-36209). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Programming Tool Software

Name

Jerryscript

Version

License

free

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CNA Base Score: 5.5
CNA Vector: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Assertion
CWE: CWE-617
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/29/2023 🔍
05/12/2023 +13 days 🔍
05/12/2023 +0 days 🔍
12/29/2025 +962 days 🔍

Sourcesinfo

Advisory: 5070
Status: Confirmed

CVE: CVE-2023-31920 (🔍)
GCVE (CVE): GCVE-0-2023-31920
GCVE (VulDB): GCVE-100-228925
EUVD: 🔍

Entryinfo

Created: 05/12/2023 17:34
Updated: 12/29/2025 12:41
Changes: 05/12/2023 17:34 (38), 06/08/2023 13:30 (9), 01/24/2025 18:09 (24), 12/29/2025 12:41 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.