{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2446 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2009-2446 is a high-severity vulnerability in Mysql Mysql, published on 13 Jul 2009. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-2446 and fix it if it is affected.\n\nWhat it is: CVE-2009-2446 is a high-severity vulnerability in Mysql Mysql, published on 13 Jul 2009. 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-2009-2446 exists.\n\nAffected product: Mysql Mysql. 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-2009-2446/ (Markdown: https://insights.sbomify.com/CVE-2009-2446/index.md)","id":"CVE-2009-2446","markdown":"https://insights.sbomify.com/CVE-2009-2446/index.md","name":"CVE-2009-2446","record":{"aliases":["DSA-1877-1","GHSA-q8wr-mc75-9wjp"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL database server","requires_auth":"low_privilege","summary":"Authenticated users can crash the MySQL daemon or potentially execute code via format string vulnerabilities in database creation or deletion commands.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mysql","vendor":"mysql"},{"product":"mysql","vendor":"oracle"}],"cvss":{"score":8.5,"severity":"high","source":"nvd","vector":"AV:N/AC:M/Au:S/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-134","name":"Use of Externally-Controlled Format String"}],"description":"Multiple format string vulnerabilities in the dispatch_command function in libmysqld/sql_parse.cc in mysqld in MySQL 4.0.0 through 5.0.83 allow remote authenticated users to cause a denial of service (daemon crash) and possibly have unspecified other impact via format string specifiers in a database name in a (1) COM_CREATE_DB or (2) COM_DROP_DB request.  NOTE: some of these details are obtained from third party information.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-06-08","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-06-08","kind":"exploitdb","ref":"33077","stars":null,"title":"MySQL 5.0.75 - 'sql_parse.cc' Multiple Format String Vulnerabilities"}],"tier":"weaponised"},"has_fix":true,"headline":"Other in n/a","id":"CVE-2009-2446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mysql:mysql","products":["mysql:mysql","oracle:mysql"],"type":"other","year":"2009"},"n_packages":0,"n_references":18,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2009-2447"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2009-2445"},"products":["n/a"],"published":"2009-07-13","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2004-0627","kev_date_added":null,"published":"2004-07-08"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0628","kev_date_added":null,"published":"2004-07-08"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2012-0553","kev_date_added":null,"published":"2013-03-28"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2013-1492","kev_date_added":null,"published":"2013-03-28"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2012-0882","kev_date_added":null,"published":"2012-12-21"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2006-2753","kev_date_added":null,"published":"2006-06-01"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Authenticated users can crash the MySQL daemon or potentially execute code via format string vulnerabilities in database creation or deletion commands.","url":"https://insights.sbomify.com/CVE-2009-2446/"}