CVE-2006-5339: Unspecified vulnerability in Oracle Spatial component in Oracle Database 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10....

Unspecified vulnerability in Oracle Spatial component in Oracle Database 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10.1.0.4 has unknown impact and remote authenticated attack vectors related to mdsys.sdo_geom, aka Vuln# DB11. NOTE: as of 20061023, Oracle has not disputed reports from reliable third parties that DB11 is related to "length checking" in the RELATE function before MD2.RELATE is called.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 19:48 UTC (UTC+00:00)

Analyst readout for executives and security teams

Plain-English summary

This is an old Oracle Database Spatial issue in several 8i, 9i, and 10g releases. The public record says an authenticated remote user may trigger an unspecified flaw in MDSYS.SDO_GEOM, but the impact is not documented. Treat it as legacy database risk needing inventory and patch verification.

Executive priority

Prioritize if legacy Oracle databases remain in production, especially where many users or applications can connect remotely. If those versions are absent, this CVE is mainly an archival tracking item.

Technical view

CVE-2006-5339 covers Oracle Spatial Vuln# DB11 in Oracle Database 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10.1.0.4. The description references MDSYS.SDO_GEOM and third-party reports about length checking in RELATE before MD2.RELATE. Impact and CVSS are unavailable.

Likely exposure

Exposure is most likely in legacy Oracle Database deployments with Oracle Spatial enabled and authenticated users able to access Spatial geometry functions. Internet exposure is not required by the description, but remote database connectivity increases concern.

Exploitation context

The provided sources and KEV flag do not show active exploitation. The attack vector is described as remote authenticated, with unknown impact. Evidence is incomplete, so do not assume exploit availability or business impact beyond the published record.

Researcher notes

The record is sparse: no CVSS, CWE, or documented impact. The notable technical clue is third-party reporting that DB11 relates to length checking around RELATE and MD2.RELATE. Validation should focus on version, Spatial presence, privileges, and patch state.

Mitigation direction

Check Oracle October 2006 Critical Patch Update guidance for this database line.
Upgrade unsupported Oracle Database versions to vendor-supported releases where possible.
Restrict remote database access to trusted networks and approved accounts.
Review privileges for Oracle Spatial packages and remove unnecessary access.
Monitor Oracle and database security advisories for superseding guidance.

Validation and detection

Inventory Oracle Database versions matching 8.1.7.4, 9.0.1.5, 9.2.0.7, and 10.1.0.4.
Confirm whether Oracle Spatial and MDSYS.SDO_GEOM are installed or accessible.
Review patch records for Oracle October 2006 CPU or later superseding CPUs.
Identify authenticated users or applications with Spatial function access.
Review logs for unusual authenticated Spatial package usage.

Prepared: Jun 29, 2026, 09:52 UTC (UTC+00:00)
Confidence: medium
Sources: 5

Public sources used

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2006-5339 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Oct 18, 2006, 01:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

11Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
http://www.red-database-security.com/advisory/oracle_cpu_oct_2006.htmlCVE reference · x_refsource_MISC
20588CVE reference · vdb-entry, x_refsource_BID
HPSBMA02133CVE reference · vendor-advisory, x_refsource_HP
http://www.oracle.com/technetwork/topics/security/cpuoct2006-095368.htmlCVE reference · x_refsource_CONFIRM
http://www.databasesecurity.com/oracle/OracleOct2006-CPU-Analysis.pdfCVE reference · x_refsource_MISC
20061018 Analysis of the Oracle October 2006 Critical Patch UpdateCVE reference · mailing-list, x_refsource_BUGTRAQ
ADV-2006-4065CVE reference · vdb-entry, x_refsource_VUPEN
22396CVE reference · third-party-advisory, x_refsource_SECUNIA
1017077CVE reference · vdb-entry, x_refsource_SECTRACK
TA06-291ACVE reference · third-party-advisory, x_refsource_CERT

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.