dbcve.org
Database ServerDatabase / datastore · Oracle

CVE-2007-2116

HIGH · 9.0 CVSS v2.0 Published 2007-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
Unspecified vulnerability in the Advanced Replication component in Oracle Database 9.0.1.5+, 9.2.0.7, and 10.1.0.5 has unknown impact and attack vectors, aka DB10. NOTE: as of 20070424, Oracle has not disputed claims that these are buffer overflows in kkzi.o for the SYS.DBMS_SNAP_INTERNAL package using the (1) SNAP_OWNER or (2) SNAP_NAME parameters.

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

Buffer overflow vulnerability in Oracle Database Advanced Replication component (SYS.DBMS_SNAP_INTERNAL package in kkzi.o) affecting SNAP_OWNER and SNAP_NAME parameters. Present in versions 9.0.1.5+, 9.2.0.7, and 10.1.0.5. The high CVSS score suggests potential for remote code execution or complete database compromise.

MitigationApply Oracle Critical Patch Updates for this vulnerability. If patching is not feasible, restrict access to the DBMS_SNAP_INTERNAL package and disable Advanced Replication features if not required.

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.7= 10.2.0.1

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

AV:N/AC:L/Au:S/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 Database version
    Execute: SELECT * FROM V$VERSION WHERE BANNER LIKE 'Oracle%'; or SELECT VERSION FROM V$INSTANCE;
    Affected if The version is 9.0.1.5, 9.2.0.7, or 10.2.0.1 exactly (or falls within the range if broader interpretation applies)
  2. Verify Advanced Replication component is installed
    Execute: SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY WHERE COMP_NAME LIKE '%Replication%';
    Affected if The component shows as VALID and installed, meaning Advanced Replication is enabled
  3. Confirm DBMS_SNAP_INTERNAL package exists
    Execute: SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS WHERE OBJECT_NAME = 'DBMS_SNAP_INTERNAL';
    Affected if The package exists in the database schema (typically under SYS)
  4. Check if current user has execute access to DBMS_SNAP_INTERNAL
    Execute: SELECT GRANTEE, TABLE_NAME, PRIVILEGE FROM DBA_TAB_PRIVS WHERE TABLE_NAME = 'DBMS_SNAP_INTERNAL';
    Affected if Users other than SYS have execute privileges, indicating potential attack surface

You are affected if your Oracle Database version matches 9.0.1.5, 9.2.0.7, or 10.2.0.1 AND Advanced Replication is installed with the DBMS_SNAP_INTERNAL package accessible to non-admin users.

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 Updates for this vulnerability. If patching is not feasible, restrict access to the DBMS_SNAP_INTERNAL package and disable Advanced Replication features if not required.

Recommended fix Moderate confidence

Apply Oracle CPU April 2007 or later; for 9.0.1.x upgrade to 9.0.1.6+, for 9.2.0.x upgrade to 9.2.0.8+, for 10.1.0.x upgrade to 10.1.0.6+

  1. 1. Identify the exact Oracle Database release and patch level by querying SELECT VERSION FROM V$INSTANCE;
  2. 2. Apply the Oracle Critical Patch Update (CPU) released in April 2007 or later, which contains the fix for CVE-2007-2116
  3. 3. For Oracle 9.0.1.x: Apply patch set 9.0.1.6 or later
  4. 4. For Oracle 9.2.0.x: Apply patch set 9.2.0.8 or later
  5. 5. For Oracle 10.1.0.x: Apply patch set 10.1.0.6 or later
  6. 6. After applying the patch, restart the database services
  7. 7. Verify the fix by confirming the patch is applied: opatch lsinventory
  8. 8. Test the Advanced Replication functionality to ensure no regression
Caveat Patch application may require downtime; always test patches in non-production environment first; older patch sets may have compatibility issues with custom applications

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

Fix this in Database Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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