Oracle9i 9.0/9.0.1/9.0.1.2/9.0.1.3/9.0.2 Authentication ORACLE.EXE Username memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Oracle9i 9.0/9.0.1/9.0.1.2/9.0.1.3/9.0.2. Affected is an unknown function of the file ORACLE.EXE of the component Authentication. This manipulation of the argument Username causes memory corruption. This vulnerability appears as CVE-2003-0095. In addition, an exploit is available.
Details
A vulnerability has been found in Oracle9i 9.0/9.0.1/9.0.1.2/9.0.1.3/9.0.2 (Database Software) and classified as very critical. Affected by this vulnerability is some unknown processing of the file ORACLE.EXE of the component Authentication. The manipulation of the argument Username with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in ORACLE.EXE for Oracle Database Server 9i, 8i, 8.1.7, and 8.0.6 allows remote attackers to execute arbitrary code via a long username that is provided during login, as exploitable through client applications that perform their own authentication, as demonstrated using LOADPSP.
The weakness was presented 02/16/2003 by Mark Litchfield as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. This vulnerability is known as CVE-2003-0095. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/25/2025).
After immediately, there has been an exploit disclosed. It is declared as proof-of-concept. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19079 (Oracle Database Server ORACLE.EXE Buffer Overflow Vulnerability).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Attack attempts may be identified with Snort ID 2650. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 3587.
The vulnerability is also documented in the databases at X-Force (11328), SecurityFocus (BID 6849†), OSVDB (6319†), Secunia (SA7443†) and Vulnerability Center (SBV-3952†). See VDB-20174 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.4
VulDB Base Score: 10.0
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Snort ID: 2650
Snort Message: SERVER-ORACLE user name buffer overflow attempt
Snort Class: 🔍
TippingPoint: 🔍
McAfee IPS: 🔍
McAfee IPS Version: 🔍
SourceFire IPS: 🔍
ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Timeline
11/05/2002 🔍01/01/2003 🔍
02/11/2003 🔍
02/16/2003 🔍
02/16/2003 🔍
03/03/2003 🔍
03/14/2004 🔍
04/09/2004 🔍
08/07/2014 🔍
08/25/2025 🔍
Sources
Advisory: kb.cert.orgResearcher: Mark Litchfield
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2003-0095 (🔍)
GCVE (CVE): GCVE-0-2003-0095
GCVE (VulDB): GCVE-100-20173
CERT: 🔍
X-Force: 11328
SecurityFocus: 6849 - Oracle Database Server ORACLE.EXE Buffer Overflow Vulnerability
Secunia: 7443 - Oracle remotely exploitable buffer overflow, Highly Critical
OSVDB: 6319 - Oracle Database Server Remote username Overflow
Vulnerability Center: 3952 - Buffer Overflow in Oracle Database Server, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 08/07/2014 18:09Updated: 08/25/2025 04:40
Changes: 08/07/2014 18:09 (76), 05/20/2019 14:14 (4), 10/28/2024 18:46 (16), 08/25/2025 04:40 (2)
Complete: 🔍
Cache ID: 216:810:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.