Exiv2 0.27 image.cpp printTiffStructure 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.5$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Exiv2 0.27. Affected is the function Exiv2::Image::printTiffStructure of the file image.cpp. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2019-9143. The attack is possible to be carried out remotely. No exploit exists. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Detailsinfo

A vulnerability was found in Exiv2 0.27 (Image Processing Software) and classified as critical. This issue affects the function Exiv2::Image::printTiffStructure of the file image.cpp. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in Exiv2 0.27. There is infinite recursion at Exiv2::Image::printTiffStructure in the file image.cpp. This can be triggered by a crafted file. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact.

The bug was discovered 02/25/2019. The weakness was disclosed 02/25/2019 (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2019-9143 since 02/25/2019. The attack may be initiated remotely. No form of authentication is needed for a successful 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.

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

The entry VDB-131208 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/25/2019 🔍
02/25/2019 +0 days 🔍
02/25/2019 +0 days 🔍
02/26/2019 +1 days 🔍
07/19/2023 +1604 days 🔍

Sourcesinfo

Advisory: 711⛔
Status: Not defined

CVE: CVE-2019-9143 (🔍)
GCVE (CVE): GCVE-0-2019-9143
GCVE (VulDB): GCVE-100-131207
SecurityFocus: 107161

See also: 🔍

Entryinfo

Created: 02/26/2019 08:48 AM
Updated: 07/19/2023 04:50 PM
Changes: 02/26/2019 08:48 AM (55), 05/13/2020 02:19 PM (2), 07/19/2023 04:50 PM (4)
Complete: 🔍
Cache ID: 244:FAC:40

Discussion

 usr3070 (+0)
7 years ago
I'd say here C and I should be N because there is no any loss of confidentiality and integrity. There is only infinite recursion which will result in DOS at minimal level only to to the application stack.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!