{"answers":{"affected":"It affects 3 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1375 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2002-1375 is a high-severity memory corruption vulnerability in Oracle Mysql, published on 1 Sep 2004. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1375 and fix it if it is affected.\n\nWhat it is: CVE-2002-1375 is a high-severity memory corruption vulnerability in Oracle Mysql, published on 1 Sep 2004. 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-2002-1375 exists.\n\nAffected product: Oracle 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-2002-1375/ (Markdown: https://insights.sbomify.com/CVE-2002-1375/index.md)","id":"CVE-2002-1375","markdown":"https://insights.sbomify.com/CVE-2002-1375/index.md","name":"CVE-2002-1375","record":{"aliases":["GHSA-gvcx-q88q-m695"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL database","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary code via a long response in the COM_CHANGE_USER command, affecting MySQL database servers.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mysql","vendor":"oracle"},{"product":"netbackup_advanced_reporter","vendor":"symantec_veritas"},{"product":"netbackup_global_data_manager","vendor":"symantec_veritas"}],"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":"The COM_CHANGE_USER command in MySQL 3.x before 3.23.54, and 4.x to 4.0.6, allows remote attackers to execute arbitrary code via a long response.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2002-12-12","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2002-12-12","kind":"exploitdb","ref":"22085","stars":null,"title":"MySQL 3.23.x/4.0.x - COM_CHANGE_USER Password Memory Corruption"}],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2002-1375","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:mysql","products":["oracle:mysql"],"type":"memory_corruption","year":"2002"},"n_packages":0,"n_references":16,"next":{"headline":"Memory corruption in n/a","id":"CVE-2002-1376"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2002-1374"},"products":["n/a"],"published":"2004-09-01","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2016-0639","kev_date_added":null,"published":"2016-04-21"},{"cvss_score":9,"headline":"Privilege escalation in n/a","id":"CVE-2003-0150","kev_date_added":null,"published":"2003-03-21"},{"cvss_score":8.5,"headline":"Denial of service in n/a","id":"CVE-2005-2572","kev_date_added":null,"published":"2005-08-16"},{"cvss_score":8,"headline":"Auth bypass in MySQL Server","id":"CVE-2020-14878","kev_date_added":null,"published":"2020-10-21"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2002-0969","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":7.7,"headline":"Denial of service in n/a","id":"CVE-2016-3440","kev_date_added":null,"published":"2016-07-21"},{"cvss_score":7.5,"headline":"MySQL Connector/Python connector takeover vulnerability","id":"CVE-2024-21272","kev_date_added":null,"published":"2024-10-15"}],"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-08","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via a long response in the COM_CHANGE_USER command, affecting MySQL database servers.","url":"https://insights.sbomify.com/CVE-2002-1375/"}