{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0549 exists.","fix":"No fix has been published for CVE-2006-0549 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0549 is a high-severity SQL injection vulnerability in Oracle Database Server, published on 4 Feb 2006. It can be exploited over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-0549 and fix it if it is affected.\n\nWhat it is: CVE-2006-0549 is a high-severity SQL injection vulnerability in Oracle Database Server, published on 4 Feb 2006. It can be exploited 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-0549 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-0549/ (Markdown: https://insights.sbomify.com/CVE-2006-0549/index.md)","id":"CVE-2006-0549","markdown":"https://insights.sbomify.com/CVE-2006-0549/index.md","name":"CVE-2006-0549","record":{"aliases":["GHSA-ff55-4qfm-2hmv"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Oracle Database","requires_auth":"unknown","summary":"Remote attackers can execute arbitrary SQL commands in Oracle Database via the SYS.DBMS_METADATA_UTIL package, potentially compromising data integrity and confidentiality.","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":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"SQL injection vulnerability in the SYS.DBMS_METADATA_UTIL package in Oracle Database 10g, and possibly earlier versions, might allow remote attackers to execute arbitrary SQL commands via unknown vectors. NOTE: due to the lack of relevant details from the Oracle advisory, a separate CVE is being created since it cannot be conclusively proven that this issue has been addressed by Oracle.  It is possible that this is the same issue as Oracle Vuln# DB05 from the January 2006 CPU, in which case this would be subsumed by CVE-2006-0260.  However, there are some inconsistencies that make this unclear, and there is also a possibility that this is related to DB06, which is subsumed by CVE-2006-0259.","ecosystems":[],"exploits":{"exploitdb":2,"first_seen":"2007-02-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2007-02-23","kind":"exploitdb","ref":"3363","stars":null,"title":"Oracle 9i/10g - DBMS_METADATA.GET_DDL SQL Injection"},{"date":"2007-02-26","kind":"exploitdb","ref":"3377","stars":null,"title":"Oracle 9i/10g DBMS_METADATA.GET_DDL - SQL Injection (2)"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2006-0549","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":7,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-0550"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2006-0548"},"products":["n/a"],"published":"2006-02-04","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":"Remote attackers can execute arbitrary SQL commands in Oracle Database via the SYS.DBMS_METADATA_UTIL package, potentially compromising data integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2006-0549/"}