Skip to main content
Mallory
CriticalVulnerability

CVE-2006-3698: SQL Injection in Oracle Database 10.1.0.5 CDC and Data Pump Metadata API

Published Jul 19, 2006 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS7.0%94th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Oracle Corporation
IdentifiersCVE-2006-3698CWE-89

CVE-2006-3698 refers to multiple SQL injection vulnerabilities in Oracle Database 10.1.0.5, specifically in the Change Data Capture (CDC) component and the Data Pump Metadata API. The vulnerabilities affect several procedures in SYS.DBMS_CDC_IMPDP, including IMPORT_CHANGE_SET, IMPORT_CHANGE_TABLE, IMPORT_CHANGE_COLUMN, IMPORT_SUBSCRIBER, IMPORT_SUBSCRIBED_TABLE, IMPORT_SUBSCRIBED_COLUMN, VALIDATE_IMPORT, VALIDATE_CHANGE_SET, VALIDATE_CHANGE_TABLE, and VALIDATE_SUBSCRIPTION, as well as the MAIN procedure in SYS.KUPW$WORKER. These procedures are vulnerable to SQL injection, allowing attackers to execute arbitrary SQL commands with the privileges of the database user.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of these vulnerabilities could allow an attacker to execute arbitrary SQL code in the context of the Oracle Database, potentially leading to data manipulation, privilege escalation, or compromise of the database integrity and confidentiality.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the affected procedures to trusted users only. Use Oracle's security best practices to limit database user privileges and monitor for suspicious activity. Where possible, disable or remove unnecessary components such as CDC or Data Pump Metadata API if not required.

Remediation

Patch, then assume compromise.

Apply the relevant Oracle Critical Patch Update (CPU) that addresses these vulnerabilities. Oracle regularly releases security patches for supported versions; ensure that the latest patches for Oracle Database 10.1.0.5 are applied.

Public exploits

Exploits

No validated public exploits yet. Hidden: 3 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationDatabase Serverapplication
FAQ

Frequently asked questions

Is CVE-2006-3698 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2006-3698 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2006-3698?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2006-3698. 3 candidate exploit records are not yet analyzed.
Is there a patch for CVE-2006-3698?
Apply the relevant Oracle Critical Patch Update (CPU) that addresses these vulnerabilities. Oracle regularly releases security patches for supported versions; ensure that the latest patches for Oracle Database 10.1.0.5 are applied.
What products are affected by CVE-2006-3698?
Oracle Corporation Database Server.
How severe is CVE-2006-3698?
CVE-2006-3698 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 7.0% (94th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.