Oracle Database Server 9.0.1.5 memory corruption ⚔ [Disputed]

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

Summaryinfo

A vulnerability has been found in Oracle Database Server 9.0.1.5 and classified as critical. The impacted element is an unknown function. The manipulation leads to memory corruption. This vulnerability is listed as CVE-2007-2118. The attack may be initiated remotely. There is no available exploit. The presence of this vulnerability remains uncertain at this time.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Oracle Database Server 9.0.1.5 (Database Software). This issue affects an unknown part. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Unspecified vulnerability in the Upgrade/Downgrade component of Oracle Database 9.0.1.5 and 9.2.0.7 has unknown impact and attack vectors, aka DB13. NOTE: as of 20070424, Oracle has not disputed reliable claims that this is a buffer overflow involving the "mig utility."

The weakness was presented 04/18/2007 by Esteban Martinez Fayo (Paul) with Application Security, Inc. (Website). It is possible to read the advisory at us-cert.gov. The identification of this vulnerability is CVE-2007-2118 since 04/18/2007. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/14/2021).

It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 56056 (Oracle Database Multiple Vulnerabilities (April 2007 CPU)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19216 (Oracle April 2007 Security Update Multiple Vulnerabilities).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (33809), Tenable (56056), SecurityFocus (BID 23532†), SecurityTracker (ID 1017927†) and Vulnerability Center (SBV-14896†). See VDB-3024, VDB-36358, VDB-36279 and VDB-36278 for similar entries. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

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.9

VulDB Base Score: 7.3
VulDB Temp Score: 6.9
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: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 56056
Nessus Name: Oracle Database Multiple Vulnerabilities (April 2007 CPU)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/17/2007 🔍
04/17/2007 +0 days 🔍
04/18/2007 +1 days 🔍
04/18/2007 +0 days 🔍
04/18/2007 +0 days 🔍
04/18/2007 +0 days 🔍
04/22/2007 +4 days 🔍
03/13/2015 +2882 days 🔍
07/14/2021 +2315 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: us-cert.gov
Researcher: Esteban Martinez Fayo (Paul)
Organization: Application Security, Inc.
Status: Confirmed
Confirmation: 🔍
Disputed: 🔍

CVE: CVE-2007-2118 (🔍)
GCVE (CVE): GCVE-0-2007-2118
GCVE (VulDB): GCVE-100-36263
X-Force: 33809
SecurityFocus: 23532 - Oracle April 2007 Security Update Multiple Vulnerabilities
SecurityTracker: 1017927 - Oracle Database and Other Products Have Unspecified Vulnerabilities With Unspecified Impact
Vulnerability Center: 14896 - Oracle Database Unspecified Upgrade/Downgrade Component Vulnerability, Info
Vupen: ADV-2007-1426

See also: 🔍

Entryinfo

Created: 03/13/2015 14:56
Updated: 07/14/2021 11:51
Changes: 03/13/2015 14:56 (57), 04/07/2017 17:05 (17), 07/14/2021 11:51 (2)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!