{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2006-1517 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2006-1517 is a medium-severity vulnerability in Mysql Mysql, published on 5 May 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-1517 and fix it if it is affected.\n\nWhat it is: CVE-2006-1517 is a medium-severity vulnerability in Mysql Mysql, published on 5 May 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-1517 in the wild and no public exploit code.\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-2006-1517/ (Markdown: https://insights.sbomify.com/CVE-2006-1517/index.md)","id":"CVE-2006-1517","markdown":"https://insights.sbomify.com/CVE-2006-1517/index.md","name":"CVE-2006-1517","record":{"aliases":["GHSA-mj77-c683-gmx7"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL database server","requires_auth":"low_privilege","summary":"Remote attackers can obtain sensitive memory information via a malformed COM_TABLE_DUMP request in MySQL.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"debian","cpe":[{"product":"mysql","vendor":"mysql"},{"product":"mysql","vendor":"oracle"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"sql_parse.cc in MySQL 4.0.x up to 4.0.26, 4.1.x up to 4.1.18, and 5.0.x up to 5.0.20 allows remote attackers to obtain sensitive information via a COM_TABLE_DUMP request with an incorrect packet length, which includes portions of memory in an error message.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2006-1517","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mysql:mysql","products":["mysql:mysql","oracle:mysql"],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":43,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-1518"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2006-1516"},"products":["n/a"],"published":"2006-05-05","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive memory information via a malformed COM_TABLE_DUMP request in MySQL.","url":"https://insights.sbomify.com/CVE-2006-1517/"}