dbcve.org
Application ServerApplication · Oracle

CVE-2008-0340

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
Multiple unspecified vulnerabilities in Oracle Database 9.0.1.5 FIPS+, 9.2.0.8, 9.2.0.8DV, 10.1.0.5, and 10.2.0.3 have unknown impact and remote attack vectors, related to the (1) Advanced Queuing component (DB02) and (2) Oracle Spatial component (DB04).

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 · high confidence

Multiple unspecified vulnerabilities in Oracle Database affecting the Advanced Queuing (DB02) and Oracle Spatial (DB04) components across versions 9.0.1.5 through 10.2.0.3. The CVSS 10 score indicates critical severity with remote unauthenticated attack vectors and unknown impact, likely allowing complete database compromise or remote code execution.

MitigationApply Oracle Critical Patch Updates (CPU) that include CVE-2008-0340 patches; for unsupported versions, upgrade to a currently supported Oracle Database release and apply latest security patches.

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 the installed Oracle product
    Query the Oracle product inventory or check Oracle Universal Installer/OPatch for installed Oracle components
    Affected if The product is one of: Oracle Database Server, Oracle Application Server, Oracle Collaboration Suite, Oracle E Business Suite, or Oracle Peoplesoft Enterprise Peopletools
  2. Determine the Oracle Database version
    Run 'SELECT VERSION FROM V$INSTANCE;' or check the ORACLE_HOME/oratab file for the installed release version
    Affected if The 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
  3. Determine the Oracle Application Server version
    Check the ORACLE_HOME inventory or run 'opatch lsinventory' for the installed release version
    Affected if The 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
  4. Determine the Oracle Collaboration Suite version
    Check the ORACLE_HOME inventory or check the product installation directories for version 10.1.2
    Affected if The version matches 10.1.2
  5. Check if Advanced Queuing (DB02) component is enabled
    Query 'SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;' to see if the Advanced Queuing component is installed and valid
    Affected if The COMP_NAME shows 'Oracle Advanced Queuing' with STATUS='VALID' on an affected database version
  6. Check if Oracle Spatial (DB04) component is enabled
    Query 'SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;' or check for MDSYS schema existence to determine if Spatial is installed
    Affected if The COMP_NAME shows 'Oracle Spatial' or 'Locator' with STATUS='VALID' on an affected database version

The environment is affected if any Oracle product matches the listed affected versions AND the Advanced Queuing or Oracle Spatial components are installed and valid.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates (CPU) that include CVE-2008-0340 patches; for unsupported versions, upgrade to a currently supported Oracle Database release and apply latest security patches.

Fix this in Application Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0340 — 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-0340 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