{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0111 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0111 is a high-severity memory corruption vulnerability in n/a, published on 19 Jan 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-2005-0111 and fix it if it is affected.\n\nWhat it is: CVE-2005-0111 is a high-severity memory corruption vulnerability in n/a, published on 19 Jan 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-2005-0111 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2005-0111/ (Markdown: https://insights.sbomify.com/CVE-2005-0111/index.md)","id":"CVE-2005-0111","markdown":"https://insights.sbomify.com/CVE-2005-0111/index.md","name":"CVE-2005-0111","record":{"aliases":["GHSA-g4q4-2gm9-m7gc"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL MaxDB","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via a stack-based buffer overflow in the websql CGI program of MySQL MaxDB.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"maxdb","vendor":"mysql"}],"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":"Stack-based buffer overflow in the websql CGI program in MySQL MaxDB 7.5.00 allows remote attackers to execute arbitrary code via a long password parameter.","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":"Memory corruption in n/a","id":"CVE-2005-0111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2005-0112"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2005-0110"},"products":["n/a"],"published":"2005-01-19","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-4305","kev_date_added":null,"published":"2006-08-30"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2005-0684","kev_date_added":null,"published":"2005-04-26"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2005-1274","kev_date_added":null,"published":"2005-04-26"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-1168","kev_date_added":null,"published":"2004-12-10"},{"cvss_score":5,"headline":"Null dereference in n/a","id":"CVE-2005-0083","kev_date_added":null,"published":"2005-03-17"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2005-0081","kev_date_added":null,"published":"2005-01-20"}],"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 execute arbitrary code via a stack-based buffer overflow in the websql CGI program of MySQL MaxDB.","url":"https://insights.sbomify.com/CVE-2005-0111/"}