CenterTools DriveLock 5.0 drivelock.exe 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.
9.5$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in CenterTools DriveLock 5.0. This affects an unknown function of the file drivelock.exe. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2007-5209. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as very critical has been found in CenterTools DriveLock 5.0. This affects some unknown functionality of the file drivelock.exe. 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 DriveLock.exe in CenterTools DriveLock 5.0 allows remote attackers to execute arbitrary code via a long HTTP request to TCP port 6061. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

The bug was discovered 10/03/2007. The weakness was shared 10/03/2007 by Parvez Anwar (Website). The advisory is shared at secunia.com. This vulnerability is uniquely identified as CVE-2007-5209 since 10/04/2007. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/27/2019).

The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 26915 (DriveLock DriveLock.exe HTTP Request Processing Remote Overflow), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows and running in the context l.

Upgrading eliminates this vulnerability.

The vulnerability is also documented in the databases at X-Force (36930), Tenable (26915), SecurityFocus (BID 25902†), OSVDB (41391†) and Secunia (SA26951†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 26915
Nessus Name: DriveLock DriveLock.exe HTTP Request Processing Remote Overflow
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/03/2007 🔍
10/03/2007 +0 days 🔍
10/03/2007 +0 days 🔍
10/03/2007 +0 days 🔍
10/03/2007 +0 days 🔍
10/03/2007 +0 days 🔍
10/04/2007 +0 days 🔍
10/04/2007 +0 days 🔍
10/04/2007 +0 days 🔍
10/08/2007 +4 days 🔍
03/16/2015 +2716 days 🔍
07/27/2019 +1594 days 🔍

Sourcesinfo

Advisory: secunia.com⛔
Researcher: Parvez Anwar
Status: Not defined

CVE: CVE-2007-5209 (🔍)
GCVE (CVE): GCVE-0-2007-5209
GCVE (VulDB): GCVE-100-39069
X-Force: 36930
SecurityFocus: 25902 - CenterTools DriveLock Remote Buffer Overflow Vulnerability
Secunia: 26951
OSVDB: 41391 - CenterTools DriveLock DriveLock.exe HTTP Request Processing Remote Overflow
Vulnerability Center: 16321 - CenterTools DriveLock Vulnerability Allows Remote Attackers to Execute Arbitrary Code, High

Entryinfo

Created: 03/16/2015 12:18
Updated: 07/27/2019 11:25
Changes: 03/16/2015 12:18 (71), 07/27/2019 11:25 (2)
Complete: 🔍
Cache ID: 216::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 want to use VulDB in your project?

Use the official API to access entries easily!