LibRaw up to 0.18.1 dcraw_common.cpp parse_tiff_ifd 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.
6.4$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in LibRaw up to 0.18.1. The impacted element is the function parse_tiff_ifd of the file internal/dcraw_common.cpp. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2017-6887. The attack requires a local approach. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in LibRaw up to 0.18.1 (Image Processing Software). It has been classified as critical. This affects the function parse_tiff_ifd of the file internal/dcraw_common.cpp. 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. The summary by CVE is:

A boundary error within the "parse_tiff_ifd()" function (internal/dcraw_common.cpp) in LibRaw versions before 0.18.2 can be exploited to cause a memory corruption via e.g. a specially crafted KDC file with model set to "DSLR-A100" and containing multiple sequences of 0x100 and 0x14A TAGs.

The bug was discovered 03/10/2017. The weakness was disclosed 05/16/2017 by Hossein Lotfi with Secunia Research (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2017-6887 since 03/14/2017. 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 of the vulnerability are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 67 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 100567 (openSUSE Security Update : libraw (openSUSE-2017-640)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 170055 (OpenSUSE Security Update for libraw (openSUSE-SU-2017:1460-1)).

Upgrading to version 0.18.2 eliminates this vulnerability. A possible mitigation has been published 3 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (100567) and SecurityFocus (BID 98592†). The entries VDB-101230, VDB-101231 and VDB-101426 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

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.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.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: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 100567
Nessus Name: openSUSE Security Update : libraw (openSUSE-2017-640)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for mingw-LibRaw FEDORA-2017-bce18ed3f2
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: LibRaw 0.18.2
Patch: github.com

Timelineinfo

03/10/2017 🔍
03/14/2017 +4 days 🔍
05/11/2017 +58 days 🔍
05/16/2017 +5 days 🔍
05/16/2017 +0 days 🔍
05/17/2017 +1 days 🔍
05/31/2017 +14 days 🔍
06/01/2017 +1 days 🔍
12/06/2022 +2014 days 🔍

Sourcesinfo

Product: github.com

Advisory: d7c3d2cb460be10a3ea7b32e9443a83c243b2251⛔
Researcher: Hossein Lotfi
Organization: Secunia Research
Status: Not defined

CVE: CVE-2017-6887 (🔍)
GCVE (CVE): GCVE-0-2017-6887
GCVE (VulDB): GCVE-100-101427

OVAL: 🔍

SecurityFocus: 98592 - LibRaw CVE-2017-6887 Memory Corruption Vulnerability
OSVDB: - LibRaw parse_tiff_ifd() function denial of service

See also: 🔍

Entryinfo

Created: 05/17/2017 08:03
Updated: 12/06/2022 14:27
Changes: 05/17/2017 08:03 (78), 09/29/2020 12:25 (7), 12/06/2022 14:27 (5)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!