Oracle Database Server 10.1.0.3 Scheduler Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Oracle Database Server 10.1.0.3 and classified as very critical. Affected by this vulnerability is an unknown functionality of the component Scheduler. This manipulation causes Remote Code Execution. This vulnerability is registered as CVE-2005-3440. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as very critical was found in Oracle Database Server 10.1.0.3 (Database Software). Affected by this vulnerability is an unknown part of the component Scheduler. The manipulation with an unknown input leads to a remote code execution vulnerability. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Unspecified vulnerability in Database Scheduler in Oracle Database Server 10g up to 10.1.0.3 has unknown impact and attack vectors, aka Oracle Vuln# DB08.
The weakness was published 11/02/2005 by Alexander Kornbrust with Application Security, Inc. (Website). The advisory is shared at us-cert.gov. This vulnerability is known as CVE-2005-3440. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/20/2024).
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 9111.
The vulnerability is also documented in the databases at X-Force (22790), SecurityFocus (BID 15134†) and Vulnerability Center (SBV-31017†). Similar entries are available at VDB-1826, VDB-26811, VDB-26810 and VDB-26809. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
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: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
TippingPoint: 🔍
SourceFire IPS: 🔍
ISS Proventia IPS: 🔍
Fortigate IPS: 🔍
Timeline
10/18/2005 🔍11/02/2005 🔍
11/02/2005 🔍
11/02/2005 🔍
11/02/2005 🔍
04/12/2011 🔍
03/11/2015 🔍
07/20/2024 🔍
Sources
Vendor: oracle.comAdvisory: us-cert.gov
Researcher: Alexander Kornbrust
Organization: Application Security, Inc.
Status: Not defined
Confirmation: 🔍
CVE: CVE-2005-3440 (🔍)
GCVE (CVE): GCVE-0-2005-3440
GCVE (VulDB): GCVE-100-26785
CERT: 🔍
X-Force: 22790
SecurityFocus: 15134 - Oracle October Security Update Multiple Vulnerabilities
Vulnerability Center: 31017 - Oracle Database Server 10g Database Scheduler Unspecified Vulnerability, Critical
See also: 🔍
Entry
Created: 03/11/2015 23:39Updated: 07/20/2024 09:21
Changes: 03/11/2015 23:39 (52), 04/07/2017 17:04 (10), 07/06/2021 11:03 (3), 07/20/2024 09:21 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.