VDB-247218 · CVE-2023-49463 · Issue 1042

libheif 1.17.5 /libheif/exif.cc find_exif_tag memory corruption

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 was found in libheif 1.17.5. It has been declared as critical. This issue affects the function find_exif_tag of the file /libheif/exif.cc. The manipulation results in memory corruption. This vulnerability was named CVE-2023-49463. There is no available exploit.

Detailsinfo

A vulnerability was found in libheif 1.17.5. It has been classified as critical. Affected is the function find_exif_tag of the file /libheif/exif.cc. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

libheif v1.17.5 was discovered to contain a segmentation violation via the function find_exif_tag at /libheif/exif.cc.

The weakness was presented 12/08/2023 as 1042. The advisory is available at github.com. This vulnerability is traded as CVE-2023-49463 since 11/27/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-53424). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

libheif

Version

1.17.5

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: Memory corruption
CWE: 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

11/27/2023 🔍
12/07/2023 +10 days 🔍
12/08/2023 +0 days 🔍
03/03/2026 +816 days 🔍

Sourcesinfo

Advisory: 1042
Status: Confirmed

CVE: CVE-2023-49463 (🔍)
GCVE (CVE): GCVE-0-2023-49463
GCVE (VulDB): GCVE-100-247218
EUVD: 🔍

Entryinfo

Created: 12/08/2023 00:57
Updated: 03/03/2026 23:52
Changes: 12/08/2023 00:57 (39), 12/31/2023 09:00 (11), 03/03/2026 23:52 (16)
Complete: 🔍
Cache ID: 216::103

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