Oracle Database 10g 10.2.0.3 kupf$file_int 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.
3.9$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Oracle Database 10g 10.2.0.3. Impacted is an unknown function. The manipulation of the argument kupf$file_int leads to memory corruption. This vulnerability is documented as CVE-2008-1820. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Oracle Database 10g 10.2.0.3 (Database Software) and classified as problematic. This issue affects some unknown functionality. The manipulation of the argument kupf$file_int 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 availability. The summary by CVE is:

Unspecified vulnerability in the Data Pump component in Oracle Database 9.2.0.8, 10.1.0.5, 10.2.0.3, and 11.1.0.6 has unknown impact and remote attack vectors related to KUPF$FILE_INT, aka DB11. NOTE: the previous information was obtained from the April 2008 CPU. Oracle has not commented on reliable researcher claims that DB11 is for a buffer overflow in the SYS.KUPF$FILE_INT.GET_FULL_FILENAME procedure.

The bug was discovered 04/15/2008. The weakness was released 04/16/2008 by Esteban Martinez Fayo (Portcullis) with Application Security, Inc. (Website). The advisory is shared at xforce.iss.net. The identification of this vulnerability is CVE-2008-1820 since 04/15/2008. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is required for exploitation. Technical details are known, but no exploit is available.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 56060 (Oracle Database Multiple Vulnerabilities (April 2008 CPU)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19232 (Oracle April 2008 Security Update Multiple Vulnerabilities).

Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 6063.

The vulnerability is also documented in the databases at X-Force (42036), Tenable (56060), SecurityFocus (BID 28725†), OSVDB (44514†) and Secunia (SA29829†). Entries connected to this vulnerability are available at VDB-41992, VDB-41991, VDB-41990 and VDB-41989. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 3.9

VulDB Base Score: 4.3
VulDB Temp Score: 3.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: 56060
Nessus Name: Oracle Database Multiple Vulnerabilities (April 2008 CPU)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
TippingPoint: 🔍

Timelineinfo

04/10/2008 🔍
04/15/2008 +5 days 🔍
04/15/2008 +0 days 🔍
04/15/2008 +0 days 🔍
04/15/2008 +0 days 🔍
04/16/2008 +1 days 🔍
04/16/2008 +0 days 🔍
04/16/2008 +0 days 🔍
04/17/2008 +1 days 🔍
11/16/2011 +1308 days 🔍
03/16/2015 +1216 days 🔍
08/08/2019 +1606 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: xforce.iss.net
Researcher: Esteban Martinez Fayo (Portcullis)
Organization: Application Security, Inc.
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2008-1820 (🔍)
GCVE (CVE): GCVE-0-2008-1820
GCVE (VulDB): GCVE-100-41981
X-Force: 42036
SecurityFocus: 28725 - Oracle April 2008 Critical Patch Update Multiple Vulnerabilities
Secunia: 29829
OSVDB: 44514 - CVE-2008-1820 - Oracle - Database Server - Unspecified Issue
SecurityTracker: 1019855
Vulnerability Center: 18189 - Data Pump Component in Oracle Database Unspecified Remote DoS Vulnerability DB11, Medium
Vupen: ADV-2008-1233

See also: 🔍

Entryinfo

Created: 03/16/2015 17:00
Updated: 08/08/2019 15:49
Changes: 03/16/2015 17:00 (66), 08/08/2019 15:49 (18)
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 know our Splunk app?

Download it now for free!