libgtop 2.14.5 glibtop_get_proc_map_s 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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in libgtop 2.14.5. It has been classified as problematic. This vulnerability affects the function glibtop_get_proc_map_s. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2007-0235. Furthermore, there is an exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in libgtop 2.14.5. This affects the function glibtop_get_proc_map_s. 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 glibtop_get_proc_map_s function in libgtop before 2.14.6 (libgtop2) allows local users to cause a denial of service (crash) and possibly execute arbitrary code via a process with a long filename that is mapped in its address space, which triggers the overflow in gnome-system-monitor.

The bug was discovered 01/14/2007. The weakness was shared 01/14/2007 (Website). The advisory is shared at launchpad.net. This vulnerability is uniquely identified as CVE-2007-0235 since 01/16/2007. The exploitability is told to be difficult. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details and a public exploit are known.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 67555 (Oracle Linux 4 : libgtop2 (ELSA-2007-0765)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Oracle Linux Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117490 (CentOS Security Update for libgtop2 (CESA-2007:0765)).

Upgrading to version 2.14.6 eliminates this vulnerability. A possible mitigation has been published 8 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (31522), Exploit-DB (29458), Tenable (67555), SecurityFocus (BID 22054†) and OSVDB (32815†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.9
VulDB Temp Score: 5.3
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: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 67555
Nessus Name: Oracle Linux 4 : libgtop2 (ELSA-2007-0765)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 57832
OpenVAS Name: Debian Security Advisory DSA 1255-1 (libgtop2)
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: 🔍

Upgrade: libgtop 2.14.6

Timelineinfo

01/14/2007 🔍
01/14/2007 +0 days 🔍
01/14/2007 +0 days 🔍
01/15/2007 +0 days 🔍
01/15/2007 +0 days 🔍
01/15/2007 +0 days 🔍
01/16/2007 +0 days 🔍
01/16/2007 +0 days 🔍
01/29/2007 +13 days 🔍
08/07/2007 +190 days 🔍
08/09/2007 +2 days 🔍
07/12/2013 +2164 days 🔍
03/12/2015 +608 days 🔍
06/14/2025 +3747 days 🔍

Sourcesinfo

Advisory: launchpad.net
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2007-0235 (🔍)
GCVE (CVE): GCVE-0-2007-0235
GCVE (VulDB): GCVE-100-34389

OVAL: 🔍

X-Force: 31522
SecurityFocus: 22054 - Libgtop2 Library Local Buffer Overflow Vulnerability
Secunia: 23736 - libgtop2 "glibtop_get_proc_map_s()" Buffer Overflow, Less Critical
OSVDB: 32815 - libgtop2 glibtop_get_proc_map_s() Function Filename Overflow
SecurityTracker: 1018526
Vulnerability Center: 14171 - libgtop2 Buffer Overflow via Process with a Long Filename, Medium
Vupen: ADV-2007-0185

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

Entryinfo

Created: 03/12/2015 22:21
Updated: 06/14/2025 16:31
Changes: 03/12/2015 22:21 (78), 07/14/2019 09:55 (10), 12/19/2024 13:02 (20), 06/14/2025 16:31 (4)
Complete: 🔍
Cache ID: 216:823: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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!