JerryScript 3.0.0 ecma-helpers-string.c ecma_new_ecma_string_from_utf8 assertion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in JerryScript 3.0.0 and classified as problematic. The impacted element is the function ecma_new_ecma_string_from_utf8 of the file /base/ecma-helpers-string.c. This manipulation causes assertion.
This vulnerability is handled as CVE-2021-46339. There is not any exploit available.
Details
A vulnerability classified as problematic was found in JerryScript 3.0.0. Affected by this vulnerability is the function ecma_new_ecma_string_from_utf8 of the file /base/ecma-helpers-string.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. As an impact it is known to affect availability.
The weakness was released 01/21/2022 as 4935. The advisory is shared at github.com. This vulnerability is known as CVE-2021-46339 since 01/18/2022. 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.
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: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
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: 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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/18/2022 🔍01/21/2022 🔍
01/21/2022 🔍
01/26/2022 🔍
Sources
Advisory: 4935Status: Confirmed
CVE: CVE-2021-46339 (🔍)
GCVE (CVE): GCVE-0-2021-46339
GCVE (VulDB): GCVE-100-191341
Entry
Created: 01/21/2022 12:01Updated: 01/26/2022 14:43
Changes: 01/21/2022 12:01 (37), 01/26/2022 14:41 (1), 01/26/2022 14:43 (1)
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.