{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3698 exists.","fix":"No fix has been published for CVE-2006-3698 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3698 is a critical SQL injection vulnerability in Oracle Database Server, published on 19 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-3698 and fix it if it is affected.\n\nWhat it is: CVE-2006-3698 is a critical SQL injection vulnerability in Oracle Database Server, published on 19 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-3698 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-3698/ (Markdown: https://insights.sbomify.com/CVE-2006-3698/index.md)","id":"CVE-2006-3698","markdown":"https://insights.sbomify.com/CVE-2006-3698/index.md","name":"CVE-2006-3698","record":{"aliases":["GHSA-c6w7-255v-jjv3"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Database","requires_auth":"low_privilege","summary":"SQL injection vulnerabilities in Oracle Database CDC and Data Pump components allow attackers to read or modify data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"database_server","vendor":"oracle"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Multiple unspecified vulnerabilities in Oracle Database 10.1.0.5 have unknown impact and attack vectors, aka Oracle Vuln# (1) DB01 for Change Data Capture (CDC) component and (2) DB03 for Data Pump Metadata API.  NOTE: as of 20060719, Oracle has not disputed a claim by a reliable researcher that DB01 is related to multiple SQL injection vulnerabilities in SYS.DBMS_CDC_IMPDP using the (a) IMPORT_CHANGE_SET, (b) IMPORT_CHANGE_TABLE, (c) IMPORT_CHANGE_COLUMN, (d) IMPORT_SUBSCRIBER, (e) IMPORT_SUBSCRIBED_TABLE, (f) IMPORT_SUBSCRIBED_COLUMN, (g) VALIDATE_IMPORT, (h) VALIDATE_CHANGE_SET, (i) VALIDATE_CHANGE_TABLE, and (j) VALIDATE_SUBSCRIPTION procedures, and that DB03 is for SQL injection in the MAIN procedure for SYS.KUPW$WORKER.","ecosystems":[],"exploits":{"exploitdb":3,"first_seen":"2007-01-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2007-01-23","kind":"exploitdb","ref":"3178","stars":null,"title":"Oracle 10g - SYS.KUPW$WORKER.MAIN PL / SQL Injection"},{"date":"2007-02-22","kind":"exploitdb","ref":"3358","stars":null,"title":"Oracle 10g - KUPW$WORKER.MAIN Grant/Revoke dba Permission"},{"date":"2007-02-26","kind":"exploitdb","ref":"3375","stars":null,"title":"Oracle 10g - KUPW$WORKER.MAIN SQL Injection (2)"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2006-3698","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:database_server","products":["oracle:database_server"],"type":"sql_injection","year":"2006"},"n_packages":0,"n_references":19,"next":{"headline":"Other in n/a","id":"CVE-2006-3699"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2006-3697"},"products":["n/a"],"published":"2006-07-19","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":"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":"SQL injection vulnerabilities in Oracle Database CDC and Data Pump components allow attackers to read or modify data.","url":"https://insights.sbomify.com/CVE-2006-3698/"}