| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as very critical has been found in stb up to 1.22. This affects the function stbtt__buf_seek of the file stb_truetype.h. The manipulation leads to assertion.
This vulnerability is traded as CVE-2020-6619. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in stb up to 1.22 and classified as very critical. This issue affects the function stbtt__buf_seek of the file stb_truetype.h. The manipulation with an unknown input leads to a assertion vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek.
The weakness was shared 01/08/2020. The identification of this vulnerability is CVE-2020-6619 since 01/08/2020. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/09/2020).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-148473, VDB-148472, VDB-148471 and VDB-148470 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: AssertionCWE: CWE-617
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
01/08/2020 🔍01/08/2020 🔍
01/09/2020 🔍
03/20/2024 🔍
Sources
Advisory: 863Status: Not defined
CVE: CVE-2020-6619 (🔍)
GCVE (CVE): GCVE-0-2020-6619
GCVE (VulDB): GCVE-100-148469
See also: 🔍
Entry
Created: 01/09/2020 10:27Updated: 03/20/2024 09:56
Changes: 01/09/2020 10:27 (35), 01/09/2020 10:32 (17), 03/20/2024 09:56 (18)
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.