dbcve.org
Application ServerApplication · Oracle

CVE-2008-0345

HIGH · 10.0 CVSS v2.0 Published 2008-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unspecified vulnerability in the Core RDBMS component in Oracle Database 11.1.0.6 has unknown impact and remote attack vectors, aka DB08.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Unspecified vulnerability in Oracle Database 11.1.0.6 Core RDBMS component with remote attack vectors and unknown impact. The vulnerability carries a CVSS 10 score indicating critical severity, though the exact nature of the flaw is not disclosed in Oracle's advisory.

MitigationApply Oracle Critical Patch Update (CPU) patches from January 2008 or later that address DB08; consider upgrading to a supported Oracle Database version as 11.1.0.6 is legacy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Application ServerApplication
Affected:= 1.0.2.2= 9.0.4.3= 10.1.2.0.2= 10.1.2.1.0= 10.1.2.2.0= 10.1.3.0.0= 10.1.3.1.0= 10.1.3.3.0
Collaboration SuiteApplication
Affected:= 10.1.2
Database ServerDatabase / datastore
Affected:= 9.0.1.5= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.2.0.2= 10.2.0.3= 11.1.0.6
E Business SuiteApplication
Affected:= 11.5.9= 11.5.10= 11.5.10.2= 12.0.0= 12.0.1= 12.0.2= 12.0.3
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.47= 8.48= 8.49

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Oracle Database version
    Run 'SELECT VERSION FROM V$INSTANCE;' or 'SELECT BANNER FROM V$VERSION;' as SYSDBA to get the Oracle Database version
    Affected if Version matches 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, 10.2.0.2, 10.2.0.3, or 11.1.0.6
  2. Identify installed Oracle Application Server version
    Check the Oracle Application Server installation directory for version information, or query the Oracle Application Server console for the installed version number
    Affected if Version matches 1.0.2.2, 9.0.4.3, 10.1.2.0.2, 10.1.2.1.0, 10.1.2.2.0, 10.1.3.0.0, 10.1.3.1.0, or 10.1.3.3.0
  3. Identify installed Oracle Collaboration Suite version
    Check the Oracle Collaboration Suite installation or query the product version through the Oracle Collaboration Suite administrative console
    Affected if Version is 10.1.2
  4. Identify installed Oracle E Business Suite version
    Check the Oracle E Business Suite instance information through the application's About page or query the DB version using Oracle responsibilities
    Affected if Version matches 11.5.9, 11.5.10, 11.5.10.2, 12.0.0, 12.0.1, 12.0.2, or 12.0.3
  5. Identify installed Oracle Peoplesoft Enterprise Peopletools version
    Check the PeopleSoft Enterprise Peopletools version through the PeopleSoft Configuration Manager or by querying the PSVERSION table
    Affected if Version matches 8.47, 8.48, or 8.49

A system is affected if any Oracle product is installed with a version matching exactly the versions listed in the CVE affected products, as the specific vulnerable component is not disclosed in the advisory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) patches from January 2008 or later that address DB08; consider upgrading to a supported Oracle Database version as 11.1.0.6 is legacy.

Recommended fix Moderate confidence

Upgrade to the latest supported Oracle version for the respective product line (Oracle Database 11gR2/12c, Oracle Application Server 10gR3, Oracle EBS 12.1.x or later, or Peoplesoft PeopleTools 8.50+)

  1. 1. Identify the specific Oracle product and version in your environment from the affected list (Application Server, Collaboration Suite, Database Server, E Business Suite, or Peoplesoft Enterprise Peopletools)
  2. 2. Review Oracle Critical Patch Update (CPU) advisories for January 2008 and subsequent CPUs for relevant patches
  3. 3. For Database Server: Upgrade to Oracle 11g Release 2 (11.2.0.x) or later supported version which includes security fixes for this vulnerability
  4. 4. For Application Server: Upgrade to a supported version such as Oracle Application Server 10g Release 3 (10.1.3.x) or later
  5. 5. For E Business Suite: Apply Oracle E-Business Suite Critical Patch Update January 2008 or later, or upgrade to a supported EBS version
  6. 6. For Peoplesoft Enterprise: Upgrade to Peoplesoft PeopleTools 8.50 or later which includes security fixes
  7. 7. Test the upgrade in a non-production environment before deploying to production
  8. 8. After upgrade, verify the vulnerability is remediated by reviewing Oracle alert logs and confirming patched Oracle binaries
Caveat Oracle major version upgrades may require schema migrations, application code changes, and compatibility testing; review Oracle upgrade documentation for your specific product

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-0345 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data