dbcve.org
Application ServerApplication · Oracle

CVE-2008-0343

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 9.0.1.5 FIPS+, 9.2.0.8, 9.2.0.8DV, and 10.1.0.5 has unknown impact and remote attack vectors, aka DB06.

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

Remote unauthenticated vulnerability in Oracle Spatial component allowing complete database compromise. The 'unspecified' nature of the description means the exact technical flaw is not detailed, but CVSS 10 indicates complete confidentiality, integrity, and availability impact via network exploitation.

MitigationApply Oracle Critical Patch Update (CPU) from January 2008 or later. For systems on unsupported Oracle versions (9i/10g), upgrade to a supported Oracle 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. Identify Oracle Spatial installation
    Query the database for Spatial component status. For Oracle Database, connect as SYSDBA and run: SELECT comp_name, version, status FROM dba_registry WHERE comp_name LIKE '%Spatial%';
    Affected if Spatial component is installed and status is VALID (vulnerable component present)
  2. Determine Oracle Database version
    Connect to the database and run: SELECT version FROM v$instance; or SELECT banner FROM v$version WHERE banner LIKE 'Oracle%';
    Affected if Version matches any of: 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
  3. Determine Oracle Application Server version
    Check the ORACLE_HOME installation or run: $ORACLE_HOME/Apache/Apache/bin/httpd -v or review opatch lsinventory output
    Affected if Version matches any of: 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
  4. Determine Oracle E Business Suite or PeopleSoft version
    For E Business Suite: check the edition version file or login to Oracle Applications. For PeopleSoft: SELECT version FROM psversion; or check the PeopleTools version in the system
    Affected if E Business Suite version matches: 11.5.9, 11.5.10, 11.5.10.2, 12.0.0, 12.0.1, 12.0.2, 12.0.3. PeopleSoft version matches: 8.47, 8.48, 8.49
  5. Verify Oracle Spatial network listener exposure
    Check listener.ora for Spatial-related service names and verify if the Oracle TNS listener is exposed to untrusted networks. Run: lsnrctl status and review listener configuration
    Affected if Oracle listener accepts remote connections on exposed network interfaces (not localhost/filtered)
  6. Check for applied Oracle patches
    Run opatch lsinventory in the Oracle home directory and review applied patches for January 2008 CPU or later
    Affected if No patches from January 2008 CPU or later are installed (vulnerable version remains unpatched)

Environment is affected if Oracle Spatial component is installed AND the Oracle product version matches any of the listed affected versions AND the system is network-accessible AND no January 2008 or later CPU patch has been applied.

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

Recommended fix Moderate confidence

Oracle Database 11g R2 or later (e.g., 19c or 21c); Oracle Application Server 10g R3 or Fusion Middleware; Oracle E-Business Suite 12.2+; PeopleSoft Enterprise PeopleTools 8.57+

  1. Identify the specific Oracle product component (Database Server, Application Server, E-Business Suite, or PeopleSoft) affected in your environment
  2. For Oracle Database: Upgrade to a supported version (11g R2, 12c, 18c, 19c, or 21c) that received security patches beyond the January 2008 CPU
  3. For Oracle Application Server: Migrate to Oracle Fusion Middleware supported versions
  4. For Oracle E-Business Suite: Apply the latest Oracle E-Business Suite security patches or upgrade to Oracle Cloud ERP
  5. For PeopleSoft Enterprise: Upgrade to a supported PeopleTools version (8.57 or later)
  6. After upgrading, apply the latest Critical Patch Update (CPU) for your Oracle product line
Caveat Upgrading from very old Oracle versions (9i/10g) to modern versions may require significant testing, schema modifications, and application compatibility verification; legacy integrations may need rewriting

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

Fix this in Application Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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