{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2081 exists.","fix":"No fix has been published for CVE-2006-2081 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-2081 is a medium-severity vulnerability in Oracle Database Server, published on 27 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-2081 and fix it if it is affected.\n\nWhat it is: CVE-2006-2081 is a medium-severity vulnerability in Oracle Database Server, published on 27 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2081 exists.\n\nAffected product: Oracle Database Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2006-2081/ (Markdown: https://insights.sbomify.com/CVE-2006-2081/index.md)","id":"CVE-2006-2081","markdown":"https://insights.sbomify.com/CVE-2006-2081/index.md","name":"CVE-2006-2081","record":{"aliases":["GHSA-3r8p-382h-8p7p"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Oracle Database Server","requires_auth":"low_privilege","summary":"Local users can execute arbitrary SQL queries via insecure privileges in the DBMS_EXPORT_EXTENSION package, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"database_server","vendor":"oracle"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2006-04-26","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2006-04-26","kind":"exploitdb","ref":"1719","stars":null,"title":"Oracle 10g Release 2 - 'DBMS_EXPORT_EXTENSION' SQL"},{"date":"2006-04-26","kind":"metasploit","ref":"auxiliary/sqli/oracle/dbms_export_extension","stars":null,"title":"Oracle DB SQL Injection via DBMS_EXPORT_EXTENSION"},{"date":"2007-02-05","kind":"exploitdb","ref":"3269","stars":null,"title":"Oracle 9i/10g - DBMS_EXPORT_EXTENSION SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2006-2081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:database_server","products":["oracle:database_server"],"type":"privilege_escalation","year":"2006"},"n_packages":0,"n_references":12,"next":{"headline":"Path traversal in n/a","id":"CVE-2006-2082"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-2080"},"products":["n/a"],"published":"2006-04-27","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2015-4863","kev_date_added":null,"published":"2015-10-21"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2013-1534","kev_date_added":null,"published":"2013-04-17"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-0071","kev_date_added":null,"published":"2010-01-13"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1979","kev_date_added":null,"published":"2009-10-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1985","kev_date_added":null,"published":"2009-10-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-1992","kev_date_added":null,"published":"2009-10-22"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2008-1818","kev_date_added":null,"published":"2008-04-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local users can execute arbitrary SQL queries via insecure privileges in the DBMS_EXPORT_EXTENSION package, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2006-2081/"}