CVE-2008-0345: Critical severity oracle java system application server vulnerability
Published Jan 17, 2008
·Updated
Unspecified vulnerability in the Core RDBMS component in Oracle Database 11.1.0.6 has unknown impact and remote attack vectors, aka DB08.
Affected Software
26 affected components
Oracle Application Server=1.0.2.2
Oracle Application Server=9.0.4.3
Oracle Application Server=10.1.2.0.2
Oracle Application Server=10.1.2.1.0
Oracle Application Server=10.1.2.2.0
Oracle Application Server=10.1.3.0.0
Oracle Application Server=10.1.3.1.0
Oracle Application Server=10.1.3.3.0
Oracle Collaboration Suite=10.1.2
Oracle Database server=9.0.1.5
Oracle Database server=9.2.0.8
Oracle Database server=9.2.0.8dv
Oracle Database server=10.1.0.5
Oracle Database server=10.2.0.2
Oracle Database server=10.2.0.3
Oracle Database server=11.1.0.6
Oracle E-Business Suite=11.5.9
Oracle E-Business Suite=11.5.10
Oracle E-Business Suite=11.5.10.2
Oracle E-Business Suite=12.0.0
Oracle E-Business Suite=12.0.1
Oracle E-Business Suite=12.0.2
Oracle E-Business Suite=12.0.3
Oracle PeopleSoft Enterprise PeopleTools=8.47
Oracle PeopleSoft Enterprise PeopleTools=8.48
Oracle PeopleSoft Enterprise PeopleTools=8.49
Event History
Jan 17, 2008
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2008-0345?
The severity of CVE-2008-0345 is currently unknown due to the unspecified nature of the vulnerability.
2
How can I fix CVE-2008-0345?
To fix CVE-2008-0345, it is recommended to apply any relevant updates or patches provided by Oracle for affected versions.
3
Which versions of Oracle are affected by CVE-2008-0345?
CVE-2008-0345 affects several versions of Oracle Database and Oracle Application Server, specifically Oracle Database 11.1.0.6 and other older versions.
4
What impact does CVE-2008-0345 have?
The impact of CVE-2008-0345 is unknown, but it may allow remote attackers to exploit the vulnerability.
5
Is there a workaround for CVE-2008-0345?
Currently, there are no specific workarounds documented for CVE-2008-0345; applying patches is the best mitigation approach.