dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2007-5505

HIGH · 7.5 CVSS v2.0 Published 2007-10-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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+, 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 (1) the Export component (DB02), (2) Oracle Text (DB04), (3) Oracle Text (DB05), (4) Spatial component (DB07), and (5) Advanced Security Option (DB19).

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

Multiple high-severity vulnerabilities in Oracle Database affecting Export, Oracle Text, Spatial, and Advanced Security Option components. The CVSS 7.5 indicates network-exploitable flaws allowing remote attackers to potentially compromise the database without authentication. The 'unspecified' nature means exact exploitation details are not disclosed, typical for Oracle CPU releases.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for the specific version, or upgrade to a supported Oracle Database version as Oracle 9i/10g are end-of-life. Implement network segmentation and restrict database port access as interim compensating controls.

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
Database ServerDatabase / datastore
Affected:= 9.0.1.5= 9.2.0.8= 9.2.0.8dv= 10.1.0.5= 10.2.0.3

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
Partial
Integrity
Partial
Availability
Partial

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

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. Check Oracle Database version
    Connect to the database as a privileged user (SYSDBA) and run: SELECT version FROM v$version; OR SELECT product_component_version FROM product_component_version WHERE product LIKE 'Oracle Database%';
    Affected if The version matches exactly: 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
  2. Verify if Oracle Export/Import utilities are in use
    Check for the presence of EXP/IMP or Data Pump (EXPDP/IMPDP) utility usage and associated directory objects: SELECT owner, object_name, object_type FROM dba_objects WHERE object_name IN ('EXP','IMP','EXPDP','IMPDP','DBMS_EXPORT_EXTENSION','DBMS_IMPORT_EXTENSION');
    Affected if Any of these utilities or related extension packages exist and have been used for data export operations
  3. Check if Oracle Text (ctxsys) is installed and enabled
    Query for Oracle Text schemas and objects: SELECT username FROM dba_users WHERE username='CTXSYS'; SELECT object_name, object_type FROM dba_objects WHERE owner='CTXSYS' AND ROWNUM <= 10;
    Affected if The CTXSYS schema exists with Oracle Text objects present in the database
  4. Verify if Oracle Spatial (MDSYS) is present
    Query for Spatial component schema: SELECT username FROM dba_users WHERE username='MDSYS'; SELECT count(*) as spatial_objects FROM dba_objects WHERE owner='MDSYS';
    Affected if The MDSYS schema exists and contains spatial objects, indicating Oracle Spatial is installed
  5. Check for Advanced Security Option usage
    Query for Advanced Security components: SELECT username FROM dba_users WHERE username IN ('ORACLE_OCM','SYSKM'); SELECT name, value FROM v$parameter WHERE name LIKE '%encryption%' OR name LIKE '%authentication%';
    Affected if Advanced Security Option parameters are configured or encryption wallets/authentication services are in use

The environment is affected if the Oracle Database version exactly matches one of the listed vulnerable versions (9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3) AND any of the affected components (Export, Oracle Text, Spatial, or Advanced Security Option) are installed or enabled.

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 the relevant Oracle Critical Patch Update (CPU) for the specific version, or upgrade to a supported Oracle Database version as Oracle 9i/10g are end-of-life. Implement network segmentation and restrict database port access as interim compensating controls.

Fix this in Database Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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