GNU C Library up to 2.22 sysdeps/i386/ldbl2mpn.c sprintf stack-based overflow

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.
6.2$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in GNU C Library up to 2.22. Impacted is the function sprintf of the file sysdeps/i386/ldbl2mpn.c. Such manipulation leads to stack-based overflow. This vulnerability is uniquely identified as CVE-2020-29573. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in GNU C Library up to 2.22 (Software Library) and classified as critical. Affected by this issue is the function sprintf of the file sysdeps/i386/ldbl2mpn.c. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability.

The weakness was disclosed 12/06/2020. The advisory is shared for download at sourceware.org. This vulnerability is handled as CVE-2020-29573. There are known technical details, but no exploit is available.

Upgrading to version 2.23 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: C Library 2.23

Timelineinfo

12/05/2020 🔍
12/06/2020 +1 days 🔍
12/06/2020 +0 days 🔍
12/12/2020 +6 days 🔍

Sourcesinfo

Vendor: gnu.org

Advisory: sourceware.org
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2020-29573 (🔍)
GCVE (CVE): GCVE-0-2020-29573
GCVE (VulDB): GCVE-100-165632

Entryinfo

Created: 12/06/2020 10:11
Updated: 12/12/2020 23:33
Changes: 12/06/2020 10:11 (41), 12/12/2020 23:25 (5), 12/12/2020 23:33 (18)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!