| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as very critical has been reported in stb up to 1.22. Affected by this vulnerability is the function stbtt__cff_int of the file stb_truetype.h. Performing a manipulation results in assertion.
This vulnerability is reported as CVE-2020-6617. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as very critical, was found in stb up to 1.22. This affects the function stbtt__cff_int of the file stb_truetype.h. 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_int.
The weakness was disclosed 01/08/2020. This vulnerability is uniquely identified as CVE-2020-6617 since 01/08/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing 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-148471, VDB-148470, VDB-148469 and VDB-148468 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 864Status: Not defined
CVE: CVE-2020-6617 (🔍)
GCVE (CVE): GCVE-0-2020-6617
GCVE (VulDB): GCVE-100-148467
See also: 🔍
Entry
Created: 01/09/2020 10:27Updated: 03/20/2024 09:48
Changes: 01/09/2020 10:27 (35), 01/09/2020 10:32 (17), 03/20/2024 09:48 (18)
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.