CVE-2007-2109
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 · uneditedMultiple unspecified vulnerabilities in Oracle Database 10.2.0.3 have unknown impact and remote authenticated attack vectors related to (1) Rules Manager and Expression Filter components (DB02) and (2) Oracle Streams (DB06). Note: as of 20070424, Oracle has not disputed reliable claims that DB02 is for a race condition in the RLMGR_TRUNCATE_MAINT trigger in the Rules Manager and Expression Filter components changing the AUTHID of a package from DEFINER to CURRENT_USER after a TRUNCATE call, and DB06 is for SQL injection in the DBMS_APPLY_USER_AGENT.SET_REGISTRATION_HANDLER procedure, which is later passed to the DBMS_APPLY_ADM_INTERNAL.ALTER_APPLY procedure, aka "Oracle Streams".
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 confidenceOracle Database 10.2.0.3 contains two vulnerabilities: (1) DB02 - a race condition in RLMGR_TRUNCATE_MAINT trigger in Rules Manager/Expression Filter that changes AUTHID from DEFINER to CURRENT_USER after TRUNCATE, enabling privilege escalation; (2) DB06 - SQL injection in DBMS_APPLY_USER_AGENT.SET_REGISTRATION_HANDLER procedure in Oracle Streams, passed to DBMS_APPLY_ADM_INTERNAL.ALTER_APPLY. Both require authenticated database access.
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= 10.2.0.3CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Oracle Database versionExecute: SELECT version FROM product_component_version WHERE product LIKE 'Oracle Database%'; or SELECT version FROM v$instance;Affected if version equals 10.2.0.3 exactly (only this specific version is affected)
-
Check if Rules Manager/Expression Filter is installedQuery: SELECT owner, object_name FROM dba_objects WHERE object_name = 'RLMGR_TRUNCATE_MAINT' AND object_type = 'TRIGGER';Affected if the trigger RLMGR_TRUNCATE_MAINT exists in the database (vulnerability DB02 applies)
-
Check if Oracle Streams is installedQuery: SELECT owner, object_name FROM dba_objects WHERE object_name IN ('DBMS_APPLY_USER_AGENT', 'SET_REGISTRATION_HANDLER') AND object_type = 'PROCEDURE';Affected if the DBMS_APPLY_USER_AGENT package exists (vulnerability DB06 applies)
User is affected only if running Oracle Database exactly version 10.2.0.3 AND (Rules Manager/Expression Filter is installed for DB02 OR Oracle Streams is installed for DB06), and the attacker has authenticated database access.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update April 2007 or later to address both the AUTHID privilege escalation and SQL injection. Follow least-privilege principles and restrict database user permissions to minimize attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-2109 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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