JerryScript 4e58ccf68070671e1fff5cd6673f0c1d5b80b166 lit-char-helpers.c lit_char_to_utf8_bytes memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in JerryScript 4e58ccf68070671e1fff5cd6673f0c1d5b80b166. Affected by this vulnerability is the function lit_char_to_utf8_bytes of the file jerry-core/lit/lit-char-helpers.c. Performing a manipulation results in memory corruption.
This vulnerability is known as CVE-2019-1010176. Remote exploitation of the attack is possible. No exploit is available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in JerryScript 4e58ccf68070671e1fff5cd6673f0c1d5b80b166. This affects the function lit_char_to_utf8_bytes of the file jerry-core/lit/lit-char-helpers.c. The manipulation with an unknown input 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. The summary by CVE is:
JerryScript commit 4e58ccf68070671e1fff5cd6673f0c1d5b80b166 is affected by: Buffer Overflow. The impact is: denial of service and possibly arbitrary code execution. The component is: function lit_char_to_utf8_bytes (jerry-core/lit/lit-char-helpers.c:377). The attack vector is: executing crafted javascript code. The fixed version is: after commit 505dace719aebb3308a3af223cfaa985159efae0.
The weakness was published 07/25/2019. This vulnerability is uniquely identified as CVE-2019-1010176 since 03/20/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
Applying the patch 505dace719aebb3308a3af223cfaa985159efae0 is able to eliminate this problem.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 505dace719aebb3308a3af223cfaa985159efae0
Timeline
03/20/2019 🔍07/25/2019 🔍
07/25/2019 🔍
11/07/2023 🔍
Sources
Advisory: 2476Status: Not defined
CVE: CVE-2019-1010176 (🔍)
GCVE (CVE): GCVE-0-2019-1010176
GCVE (VulDB): GCVE-100-138765
Entry
Created: 07/25/2019 21:23Updated: 11/07/2023 16:55
Changes: 07/25/2019 21:23 (37), 07/12/2020 10:34 (17), 11/07/2023 16:55 (5)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.