JerryScript 1.0 lit/lit-char-helpers.c lit_read_code_unit_from_hex memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JerryScript 1.0 and classified as critical. This issue affects the function lit_read_code_unit_from_hex of the file lit/lit-char-helpers.c. The manipulation with the input RegExp("[\x0"); results in memory corruption.
This vulnerability is cataloged as CVE-2017-18212. The attack may be launched remotely. There is no exploit available.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability was found in JerryScript 1.0. It has been classified as critical. Affected is the function lit_read_code_unit_from_hex of the file lit/lit-char-helpers.c. The manipulation with the input value RegExp("[\x0"); leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in JerryScript 1.0. There is a heap-based buffer over-read in the lit_read_code_unit_from_hex frunction in lit/lit-char-helpers.c via a RegExp("[\x0"); payload.
The bug was discovered 12/07/2017. The weakness was shared 03/01/2018 (Website). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2017-18212 since 03/01/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 84 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/07/2017 🔍03/01/2018 🔍
03/01/2018 🔍
03/01/2018 🔍
03/02/2018 🔍
02/16/2023 🔍
Sources
Advisory: 2140Status: Not defined
CVE: CVE-2017-18212 (🔍)
GCVE (CVE): GCVE-0-2017-18212
GCVE (VulDB): GCVE-100-113964
Entry
Created: 03/02/2018 07:54 AMUpdated: 02/16/2023 10:49 AM
Changes: 03/02/2018 07:54 AM (57), 01/09/2020 03:59 PM (1), 02/16/2023 10:49 AM (3)
Complete: 🔍
Cache ID: 244:861:40
No comments yet. Languages: en.
Please log in to comment.