GNU LibreDWG 0.12.5 bits.c bit_utf8_to_TU heap-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.
7.1	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in GNU LibreDWG 0.12.5. This vulnerability affects the function bit_utf8_to_TU of the file bits.c. The manipulation results in heap-based overflow. This vulnerability is known as CVE-2023-36272. No exploit is available.

Detailsinfo

A vulnerability classified as critical has been found in GNU LibreDWG 0.12.5 (Image Processing Software). Affected is the function bit_utf8_to_TU of the file bits.c. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

LibreDWG v0.12.5 was discovered to contain a heap buffer overflow via the function bit_utf8_to_TU at bits.c.

The weakness was published 06/23/2023 as 681. The advisory is available at github.com. This vulnerability is traded as CVE-2023-36272 since 06/21/2023. Technical details are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-40243). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Image Processing Software

Vendor

Name

LibreDWG

Version

0.12.5

License

open-source

Website

Vendor: https://www.gnu.org/

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.1
VulDB Meta Temp Score: 7.1

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

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / 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-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/21/2023 🔍
06/23/2023 +2 days 🔍
06/23/2023 +0 days 🔍
01/12/2026 +934 days 🔍

Sourcesinfo

Vendor: gnu.org

Advisory: 681
Status: Confirmed

CVE: CVE-2023-36272 (🔍)
GCVE (CVE): GCVE-0-2023-36272
GCVE (VulDB): GCVE-100-232290
EUVD: 🔍

Entryinfo

Created: 06/23/2023 17:35
Updated: 01/12/2026 11:19
Changes: 06/23/2023 17:35 (41), 07/18/2023 09:14 (11), 01/12/2026 11:19 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.