dbcve.org
Application ServerApplication · Oracle

CVE-2008-0344

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 Oracle Spatial component in Oracle Database 10.1.0.5 and 10.2.0.3 has unknown impact and remote attack vectors, aka DB07.

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 Spatial component affecting Oracle Database 10.1.0.5 and 10.2.0.3. The vulnerability has unknown impact but is remotely exploitable (CVSS 10). Oracle Spatial provides spatial data management and location-based services within the database.

MitigationApply Oracle Critical Patch Update (CPU) for January 2008 or later. For systems on unsupported Oracle 10g versions, upgrade to a supported database version and apply latest CPU.

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. Verify Oracle Spatial component is installed
    Query the database for Spatial components: SELECT comp_name, version, status FROM dba_registry WHERE comp_name LIKE '%Spatial%'; or check for MDSYS schema existence: SELECT username FROM dba_users WHERE username = 'MDSYS';
    Affected if Oracle Spatial is installed and the version matches one of the affected versions listed in the CVE (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 for Database Server)
  2. Check Oracle Database server version
    Connect as SYSDBA and run: SELECT version FROM v$instance; or SELECT * FROM v$version; to obtain the full version string
    Affected if The version output matches any of the affected Database Server versions: 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. Check Oracle Application Server version
    Locate the Oracle Home directory and check the version file: cat $ORACLE_HOME/oraInventory/ContentsXML/oraclehomeproperties.xml or check the OPatch inventory: $ORACLE_HOME/OPatch/opatch lsinventory
    Affected if The Application Server version matches any of the affected versions: 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. Verify Spatial features are in use
    Check for spatial indexes or spatial data: SELECT index_name FROM dba_indexes WHERE index_type = 'DOMAIN' AND ext_idx_usr = 'MDSYS'; or query USER_SDO_GEOM_METADATA for spatial layers
    Affected if Spatial indexes or spatial metadata exist, indicating the Oracle Spatial feature is actively used in the database

The environment is affected if Oracle Spatial component is installed and the Oracle product version matches any of the specific versions listed in the affected products (9.0.1.5 through 11.1.0.6 for Database, or the Application Server versions, etc.), and the system is network-accessible.

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) for January 2008 or later. For systems on unsupported Oracle 10g versions, upgrade to a supported database version and apply latest CPU.

Recommended fix Moderate confidence

Oracle Database 10.2.0.4+ or 11g release; Oracle Critical Patch Update January 2008 or later

  1. Apply the Oracle Critical Patch Update (CPU) for January 2008 or later, which addresses CVE-2008-0344 (Oracle Spatial DB07)
  2. For Oracle Database 10.1.0.5, apply Oracle patch set 10.1.0.6 or later
  3. For Oracle Database 10.2.0.3, apply Oracle patch set 10.2.0.4 or later
  4. Verify the patch was applied successfully by checking the Oracle inventory: opatch lsinventory
  5. Confirm the fix by reviewing the Oracle Critical Patch Update advisory for January 2008 at www.oracle.com/technetwork/topics/security/cpujan2008-48616.html
Caveat Patch updates are generally safe but test in non-production first; some patches may require downtime and specific pre-installation steps

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
  • Testing16.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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