stb up to 1.22 stb_truetype.h stbtt__cff_get_index assertion

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.8$0-$5k0.00

Summaryinfo

A vulnerability has been found in stb up to 1.22 and classified as very critical. The affected element is the function stbtt__cff_get_index of the file stb_truetype.h. Performing a manipulation results in assertion. This vulnerability was named CVE-2020-6623. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as very critical has been found in stb up to 1.22. This affects the function stbtt__cff_get_index 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_get_index.

The weakness was presented 01/08/2020. This vulnerability is uniquely identified as CVE-2020-6623 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 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.

See VDB-148472, VDB-148471, VDB-148470 and VDB-148469 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB 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: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Assertion
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/08/2020 🔍
01/08/2020 +0 days 🔍
01/09/2020 +1 days 🔍
03/20/2024 +1532 days 🔍

Sourcesinfo

Advisory: 865
Status: Not defined

CVE: CVE-2020-6623 (🔍)
GCVE (CVE): GCVE-0-2020-6623
GCVE (VulDB): GCVE-100-148473
See also: 🔍

Entryinfo

Created: 01/09/2020 10:28
Updated: 03/20/2024 10:11
Changes: 01/09/2020 10:28 (35), 01/09/2020 10:33 (17), 03/20/2024 10:11 (18)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!