JerryScript 2.2.0 js-parser.c parser_parse_source assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in JerryScript 2.2.0. Affected is the function parser_parse_source of the file js-parser.c. Performing a manipulation results in assertion.
This vulnerability is known as CVE-2020-23312. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability, which was classified as critical, was found in JerryScript 2.2.0. This affects the function parser_parse_source of the file js-parser.c. The manipulation with an unknown input leads to a assertion vulnerability. CWE is classifying the issue as 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 weakness was published 06/11/2021. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2020-23312. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: AssertionCWE: CWE-617
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
08/13/2020 🔍06/11/2021 🔍
06/11/2021 🔍
06/13/2021 🔍
Sources
Advisory: github.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-23312 (🔍)
GCVE (CVE): GCVE-0-2020-23312
GCVE (VulDB): GCVE-100-176835
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/11/2021 13:32Updated: 06/13/2021 13:27
Changes: 06/11/2021 13:32 (40), 06/13/2021 13:27 (3)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.