{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-3682 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2010-3682 is a medium-severity vulnerability in Mysql Mysql, published on 11 Jan 2011. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2010-3682 and fix it if it is affected.\n\nWhat it is: CVE-2010-3682 is a medium-severity vulnerability in Mysql Mysql, published on 11 Jan 2011. 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-2010-3682 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-2010-3682/ (Markdown: https://insights.sbomify.com/CVE-2010-3682/index.md)","id":"CVE-2010-3682","markdown":"https://insights.sbomify.com/CVE-2010-3682/index.md","name":"CVE-2010-3682","record":{"aliases":["GHSA-5vcg-4cg3-gq34"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL database","requires_auth":"low_privilege","summary":"Authenticated remote attackers can crash the MySQL daemon via crafted SQL statements, causing a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mysql","vendor":"mysql"},{"product":"mysql","vendor":"oracle"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Oracle MySQL 5.1 before 5.1.49 and 5.0 before 5.0.92 allows remote authenticated users to cause a denial of service (mysqld daemon crash) by using EXPLAIN with crafted \"SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...)\" statements, which triggers a NULL pointer dereference in the Item_singlerow_subselect::store function.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2010-08-20","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2010-08-20","kind":"exploitdb","ref":"34506","stars":null,"title":"MySQL 5.1.48 - 'EXPLAIN' Denial of Service"}],"tier":"weaponised"},"has_fix":true,"headline":"Null dereference in n/a","id":"CVE-2010-3682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mysql:mysql","products":["mysql:mysql","oracle:mysql"],"type":"null_dereference","year":"2010"},"n_packages":0,"n_references":25,"next":{"headline":"Denial of service in n/a","id":"CVE-2010-3683"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2010-3681"},"products":["n/a"],"published":"2011-01-11","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":8.5,"headline":"Other in n/a","id":"CVE-2009-2446","kev_date_added":null,"published":"2009-07-13"},{"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":"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 remote attackers can crash the MySQL daemon via crafted SQL statements, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2010-3682/"}