# What is CVE-2006-2081? > CVE-2006-2081 is a medium-severity flaw (CVSS 4.6) in Database Server from Oracle, published on 27 April 2006. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 22%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2006-2081 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 37 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 4.6 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 22% (latest exploit-likelihood forecast) - **Published:** 27 April 2006 - **Record last updated:** 16 June 2026 - **Main product:** Database Server from Oracle - **Affected products:** 1 ## What is CVE-2006-2081? In plain terms An attacker has to be already on the device without logging in. If it works, the attacker can read some data, change some data and slow it down. ### The official description Oracle Database Server 10g Release 2 allows local users to execute arbitrary SQL queries via the GET_DOMAIN_INDEX_METADATA function in the DBMS_EXPORT_EXTENSION package. NOTE: this issue was originally linked to DB05 (CVE-2006-1870), but a reliable third party has claimed that it is not the same issue. Based on details of the problem, the primary issue appears to be insecure privileges that facilitate the introduction of SQL in a way that is not related to special characters, so this is not "SQL injection" per se. ### What kind of flaw is it? - Unknown: Unknown ### How an attack on it works - Where an attacker can be: Already on the device - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - What an attacker gets: Can read some data, change some data and slow it down Severity vector: `AV:L/AC:L/Au:N/C:P/I:P/A:P` ## Is CVE-2006-2081 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 22%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 22%, 22%, 22%, 22%, 22%, 22%, 22%. ### Timeline - 27 April 2006: Published - 16 June 2026: Exploit likelihood fell - 16 June 2026: Record last updated ### How Precursor Intelligence ranks it CVE-2006-2081 scores **37 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2006-2081? The published record lists 1 product. - [Database Server](https://www.precursorintelligence.com/product/oracle/database_server) by [Oracle](https://www.precursorintelligence.com/vendors/oracle) (Application): all versions ## How do I fix CVE-2006-2081? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [secunia.com](http://secunia.com/advisories/19860) - [securityreason.com](http://securityreason.com/securityalert/802) - [securitytracker.com](http://securitytracker.com/id?1015999) - [kb.cert.org](http://www.kb.cert.org/vuls/id/932124) (Government resource) - [red-database-security.com](http://www.red-database-security.com/exploits/oracle-sql-injection-oracle-dbms_export_extension.html) (Exploit) - [securityfocus.com](http://www.securityfocus.com/archive/1/431353/100/0/threaded) - [securityfocus.com](http://www.securityfocus.com/archive/1/432078/100/0/threaded) - [securityfocus.com](http://www.securityfocus.com/archive/1/432354/100/0/threaded) - [securityfocus.com](http://www.securityfocus.com/archive/1/432355/100/0/threaded) - [securityfocus.com](http://www.securityfocus.com/archive/1/432632/30/5250/threaded) - [securityfocus.com](http://www.securityfocus.com/bid/17699) - [exchange.xforce.ibmcloud.com](https://exchange.xforce.ibmcloud.com/vulnerabilities/26048) ## Questions ### What is CVE-2006-2081? CVE-2006-2081 is a medium-severity flaw in Database Server from Oracle, published on 27 April 2006. An attacker has to be already on the device without logging in. If it works, the attacker can read some data, change some data and slow it down. ### How serious is CVE-2006-2081? It scores 4.6 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2006-2081 is 37 out of 100, which is Low. Its action is "Monitor". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2006-2081 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 22%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2006-2081 affect? For Database Server from Oracle: all versions. ### How do I fix CVE-2006-2081? Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2006-2081 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact