GIMP 1.18beta2 numeric error

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.
9.0$0-$5k0.00

Summaryinfo

A vulnerability was found in GIMP 1.18beta2. It has been classified as critical. The impacted element is an unknown function. Performing a manipulation results in numeric error. This vulnerability is identified as CVE-2009-0723. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in GIMP 1.18beta2 (Image Processing Software). This affects an unknown code block. The manipulation with an unknown input leads to a numeric error vulnerability. CWE is classifying the issue as CWE-189. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Multiple integer overflows in LittleCMS (aka lcms or liblcms) before 1.18beta2, as used in Firefox 3.1beta, OpenJDK, and GIMP, allow context-dependent attackers to execute arbitrary code via a crafted image file that triggers a heap-based buffer overflow. NOTE: some of these details are obtained from third party information.

The bug was discovered 03/19/2009. The weakness was released 03/23/2009 by Chris Evans with Google Security Team (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2009-0723 since 02/24/2009. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 43736 (CentOS 5 : java-1.6.0-openjdk (CESA-2009:0377)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 155950 (Oracle Enterprise Linux Update for lcms (ELSA-2009-0339)).

Upgrading 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 X-Force (49347), Tenable (43736), SecurityFocus (BID 34185†), OSVDB (56308†) and Secunia (SA34367†). Entries connected to this vulnerability are available at VDB-47330, VDB-47329, VDB-47326 and VDB-47325. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.0

VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Numeric error
CWE: CWE-189
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 43736
Nessus Name: CentOS 5 : java-1.6.0-openjdk (CESA-2009:0377)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 63677
OpenVAS Name: Debian Security Advisory DSA 1745-1 (lcms)
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: 🔍

Timelineinfo

02/24/2009 🔍
03/19/2009 +23 days 🔍
03/19/2009 +0 days 🔍
03/19/2009 +0 days 🔍
03/20/2009 +1 days 🔍
03/20/2009 +0 days 🔍
03/23/2009 +3 days 🔍
03/23/2009 +0 days 🔍
03/23/2009 +0 days 🔍
04/08/2009 +16 days 🔍
01/06/2010 +273 days 🔍
03/17/2015 +1896 days 🔍
11/19/2024 +3535 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Researcher: Chris Evans
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2009-0723 (🔍)
GCVE (CVE): GCVE-0-2009-0723
GCVE (VulDB): GCVE-100-47241

OVAL: 🔍

X-Force: 49347
SecurityFocus: 34185 - Little CMS Memory Leak and Multiple Memory Corruption Vulnerabilities
Secunia: 34367 - Little cms Multiple Vulnerabilities, Highly Critical
OSVDB: 56308 - CVE-2009-0723 - Little CMS - Multiple Integer Overflow Issues
SecurityTracker: 1021869
Vulnerability Center: 21369 - Little CMS < 1.18beta2 Heap-Based Buffer Overflow Vulnerability, Medium
Vupen: ADV-2009-0775

See also: 🔍

Entryinfo

Created: 03/17/2015 23:38
Updated: 11/19/2024 22:44
Changes: 03/17/2015 23:38 (85), 08/31/2019 09:51 (5), 11/19/2024 22:44 (19)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!