Oracle Database Server 9.0.1.5 sql injection ⚔ [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.0$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Oracle Database Server 9.0.1.5. Affected by this issue is some unknown functionality. The manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2007-2111. The attack is possible to be carried out remotely. No exploit exists. There are still doubts about whether this vulnerability truly exists.

Detailsinfo

A vulnerability was found in Oracle Database Server 9.0.1.5 (Database Software) and classified as critical. This issue affects an unknown code. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

SQL injection vulnerability in the SYS.DBMS_AQADM_SYS package in Oracle Database 9.0.1.5, 9.2.0.7, and 10.1.0.5 allows remote authenticated users to inject arbitrary SQL commands via unknown vectors, aka DB04. NOTE: as of 20070424, Oracle has not disputed reliable claims that DB04 is actually for multiple vulnerabilities.

The weakness was disclosed 04/18/2007 by Esteban Martinez Fayo (Paul) with Application Security, Inc. (Website). The advisory is shared at us-cert.gov. The identification of this vulnerability is CVE-2007-2111 since 04/18/2007. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

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.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 5365.

The vulnerability is also documented in the databases at X-Force (33832), Tenable (56056), SecurityFocus (BID 23532†), SecurityTracker (ID 1017927†) and Vulnerability Center (SBV-14903†). The entries VDB-3024, VDB-36358, VDB-36279 and VDB-36278 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best 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: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
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: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
TippingPoint: 🔍

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-2111 (🔍)
GCVE (CVE): GCVE-0-2007-2111
GCVE (VulDB): GCVE-100-36257
X-Force: 33832
SecurityFocus: 23532 - Oracle April 2007 Security Update Multiple Vulnerabilities
SecurityTracker: 1017927 - Oracle Database and Other Products Have Unspecified Vulnerabilities With Unspecified Impact
Vulnerability Center: 14903 - Oracle Database SYS.DBMS_AQADM_SYS package SQL Injection Vulnerability, Medium
Vupen: ADV-2007-1426

See also: 🔍

Entryinfo

Created: 03/13/2015 14:56
Updated: 07/14/2021 11:05
Changes: 03/13/2015 14:56 (56), 04/07/2017 17:05 (17), 07/14/2021 11:05 (2)
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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!