dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2007-3855

MEDIUM · 6.5 CVSS v2.0 Published 2007-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 allows remote authenticated users to have an unknown impact via (1) SYS.DBMS_DRS in the DataGuard component (DB03), (2) SYS.DBMS_STANDARD in the PL/SQL component (DB10), (3) MDSYS.RTREE_IDX in the Spatial component (DB16), and (4) SQL Compiler (DB17). NOTE: a reliable researcher claims that DB17 is for using Views to perform unauthorized insert, update, or delete actions.

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 9i and 10g allow authenticated remote users to impact data integrity via four vectors: SYS.DBMS_DRS (DataGuard), SYS.DBMS_STANDARD (PL/SQL), MDSYS.RTREE_IDX (Spatial), and SQL Compiler (Views allowing unauthorized INSERT/UPDATE/DELETE). The vulnerabilities require authentication but can be exploited remotely.

MitigationApply Oracle Critical Patch Update (CPU) for July 2007 or later to address these vulnerabilities. If immediate patching is not feasible, restrict database user privileges to minimum required and audit privileged user activities.

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

AV:N/AC:L/Au:S/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. Identify installed Oracle Database version
    Run SELECT version FROM v$instance; or SELECT product, version FROM product_component_version WHERE product LIKE 'Oracle Database%';
    Affected if The version matches 9.0.1.5, 9.2.0.8, 9.2.0.8dv, 10.1.0.5, or 10.2.0.3
  2. Verify existence of SYS.DBMS_DRS package
    Query SELECT owner, object_name, object_type FROM dba_objects WHERE object_name = 'DBMS_DRS' AND owner = 'SYS';
    Affected if The package exists and is accessible to the database user connecting remotely
  3. Verify existence of SYS.DBMS_STANDARD package
    Query SELECT owner, object_name, object_type FROM dba_objects WHERE object_name = 'DBMS_STANDARD' AND owner = 'SYS';
    Affected if The package exists and is accessible to the database user connecting remotely
  4. Verify existence of MDSYS.RTREE_IDX package
    Query SELECT owner, object_name, object_type FROM dba_objects WHERE object_name = 'RTREE_IDX' AND owner = 'MDSYS';
    Affected if The package exists and is accessible to the database user connecting remotely
  5. Check for overly permissive database user privileges
    Query SELECT grantee, owner, table_name, privilege FROM dba_tab_privs WHERE (table_name IN ('DBMS_DRS','DBMS_STANDARD','RTREE_IDX') OR owner IN ('SYS','MDSYS')) AND grantee NOT IN ('SYS','SYSTEM','MDSYS','ORDSYS');
    Affected if Non-privileged users have been granted execute or access privileges on the affected packages

The environment is affected if the Oracle Database version matches any of the listed versions AND authenticated remote users can access the vulnerable packages (DBMS_DRS, DBMS_STANDARD, RTREE_IDX) or exploit the SQL compiler view permissions.

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 Update (CPU) for July 2007 or later to address these vulnerabilities. If immediate patching is not feasible, restrict database user privileges to minimum required and audit privileged user activities.

Fix this in Database 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-2007-3855 — 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-3855 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