{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-1876 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-1876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-1876 is a critical SQL injection vulnerability in Oracle Database Server, published on 20 Apr 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-1876 and fix it if it is affected.\n\nWhat it is: CVE-2006-1876 is a critical SQL injection vulnerability in Oracle Database Server, published on 20 Apr 2006. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-1876 in the wild and no public exploit code.\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-1876/ (Markdown: https://insights.sbomify.com/CVE-2006-1876/index.md)","id":"CVE-2006-1876","markdown":"https://insights.sbomify.com/CVE-2006-1876/index.md","name":"CVE-2006-1876","record":{"aliases":["GHSA-cfj6-q3cc-w2mq"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Database Server","requires_auth":"low_privilege","summary":"SQL injection in Oracle Spatial functions allows attackers to read or modify database 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":9,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:S/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Unspecified vulnerability in Oracle Database Server 9.2.0.7 and 10.1.0.4 has unknown impact and attack vectors in the Oracle Spatial component, aka Vuln# DB12.  NOTE: details are unavailable from Oracle, but as of 20060421, they have not publicly disputed a claim by a reliable independent researcher that states that the problem is SQL injection in the (1) GEN_RID_RANGE_BY_AREA and (2) GEN_RID_RANGE functions in the MDSYS.SDO_PRIDX package.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2006-1876","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":12,"next":{"headline":"Other in n/a","id":"CVE-2006-1877"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-1875"},"products":["n/a"],"published":"2006-04-20","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"SQL injection in Oracle Spatial functions allows attackers to read or modify database data.","url":"https://insights.sbomify.com/CVE-2006-1876/"}