{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1921 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1921 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1921 is a high-severity vulnerability in Oracle Mysql, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1921 and fix it if it is affected.\n\nWhat it is: CVE-2002-1921 is a high-severity vulnerability in Oracle Mysql, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2002-1921 in the wild and no public exploit code.\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-1921/ (Markdown: https://insights.sbomify.com/CVE-2002-1921/index.md)","id":"CVE-2002-1921","markdown":"https://insights.sbomify.com/CVE-2002-1921/index.md","name":"CVE-2002-1921","record":{"aliases":["GHSA-c36p-446q-54r5"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL database","requires_auth":"none","summary":"Remote attackers can access the MySQL database because the default Windows configuration binds to all interfaces instead of loopback.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mysql","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":"The default configuration of MySQL 3.20.32 through 3.23.52, when running on Windows, does set the bind address to the loopback interface, which allows remote attackers to connect to the database.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Misconfiguration in n/a","id":"CVE-2002-1921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"oracle:mysql","products":["oracle:mysql"],"type":"misconfiguration","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-1922"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2002-1920"},"products":["n/a"],"published":"2005-06-28","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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Remote attackers can access the MySQL database because the default Windows configuration binds to all interfaces instead of loopback.","url":"https://insights.sbomify.com/CVE-2002-1921/"}