libtiff up to 3.8.2 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.6$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in libtiff up to 3.8.2. The impacted element is an unknown function. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2006-2656. Moreover, an exploit is present. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in libtiff up to 3.8.2 (Image Processing Software). This affects some unknown processing. 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:

Stack-based buffer overflow in the tiffsplit command in libtiff 3.8.2 and earlier might might allow attackers to execute arbitrary code via a long filename. NOTE: tiffsplit is not setuid. If there is not a common scenario under which tiffsplit is called with attacker-controlled command line arguments, then perhaps this issue should not be included in CVE.

The bug was discovered 05/24/2006. The weakness was disclosed 05/30/2006 (Website). The advisory is shared at redhat.com. This vulnerability is uniquely identified as CVE-2006-2656 since 05/30/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 22149 (RHEL 2.1 / 3 / 4 : libtiff (RHSA-2006:0603)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 156193 (Oracle Enterprise Linux Update for libtiff (ELSA-2006:0603)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 3 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (31278), Exploit-DB (1831), Tenable (22149), SecurityFocus (BID 19287†) and OSVDB (26030†). The entries VDB-31624, VDB-31623, VDB-31622 and VDB-31621 are 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

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 22149
Nessus Name: RHEL 2.1 / 3 / 4 : libtiff (RHSA-2006:0603)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 56923
OpenVAS Name: Debian Security Advisory DSA 1091-1 (tiff)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Timelineinfo

05/24/2006 🔍
05/30/2006 +6 days 🔍
05/30/2006 +0 days 🔍
05/30/2006 +0 days 🔍
05/30/2006 +0 days 🔍
06/08/2006 +9 days 🔍
06/11/2006 +3 days 🔍
08/02/2006 +52 days 🔍
08/04/2006 +2 days 🔍
03/12/2015 +3142 days 🔍
02/03/2025 +3616 days 🔍

Sourcesinfo

Product: libtiff.org

Advisory: redhat.com
Status: Confirmed

CVE: CVE-2006-2656 (🔍)
GCVE (CVE): GCVE-0-2006-2656
GCVE (VulDB): GCVE-100-30477
X-Force: 31278
SecurityFocus: 19287
Secunia: 20501 - Ubuntu update for tiff, Moderately Critical
OSVDB: 26030 - CVE-2006-2656 - Libtiff - Buffer Overflow Issue
Vulnerability Center: 11872 - Libtiff Stack Overflow via Long Filename, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/12/2015 12:19
Updated: 02/03/2025 02:02
Changes: 03/12/2015 12:19 (74), 06/20/2019 15:37 (6), 02/03/2025 02:02 (27)
Complete: 🔍
Cache ID: 216:679:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!