JerryScript 2.2.0 ecma-regexp-object.c ecma_regexp_match stack-based overflow
|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.
A vulnerability was found in JerryScript 2.2.0 and classified as critical. Affected by this issue is the function
ecma_regexp_match of the file ecma-regexp-object.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-121. Impacted is confidentiality, integrity, and availability. CVE summarizes:
There is a stack-overflow at ecma-regexp-object.c:535 in ecma_regexp_match in JerryScript 2.2.0.
The weakness was released 06/11/2021. The advisory is available at github.com. This vulnerability is handled as CVE-2020-23306 since 08/13/2020. The exploitation is known to be easy. Access to the local network is required for this attack. The requirement for exploitation is a simple authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of 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.
CVSSv3VulDB 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: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Memory corruption
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
CountermeasuresRecommended: no mitigation known
0-Day Time: 🔒
Timeline08/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
CVE: CVE-2020-23306 (🔒)
EntryCreated: 06/11/2021 01:43 PM
Updated: 06/13/2021 02:26 PM
Changes: (3) source_cve_assigned source_cve_nvd_summary advisory_confirm_url
Do you know our Splunk app?
Download it now for free!