{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4681 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4681 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4681 is a medium-severity memory corruption vulnerability in n/a, published on 1 Feb 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2005-4681 and fix it if it is affected.\n\nWhat it is: CVE-2005-4681 is a medium-severity memory corruption vulnerability in n/a, published on 1 Feb 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2005-4681 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-4681/ (Markdown: https://insights.sbomify.com/CVE-2005-4681/index.md)","id":"CVE-2005-4681","markdown":"https://insights.sbomify.com/CVE-2005-4681/index.md","name":"CVE-2005-4681","record":{"aliases":["GHSA-r862-p7gw-4jfm"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"mIRC client","requires_auth":"none","summary":"Local users can execute arbitrary code via a buffer overflow in mIRC's DCC Get Folder Dialog, though the vendor disputes this as a security vulnerability.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mirc","vendor":"khaled_mardam-bey"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in mIRC 5.91, 6.03, 6.12, and 6.16 allows local users to execute arbitrary code via a long string that is entered after reaching the DCC Get Folder Dialog.  NOTE: this issue has been disputed by the vendor, saying \"as far as I can tell, this is neither an exploit nor a vulnerability. The above report describes a local bug in mIRC.\"  It could be that this is only exploitable by the user of the application, and thus would not cross privilege boundaries unless under an otherwise restrictive environment such as a kiosk","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-4681","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2005"},"n_packages":0,"n_references":6,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-4682"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2005-4680"},"products":["n/a"],"published":"2006-02-01","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-1456","kev_date_added":null,"published":"2003-03-18"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2002-0231","kev_date_added":null,"published":"2002-05-03"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2001-0315","kev_date_added":null,"published":"2001-04-04"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-1999-0399","kev_date_added":null,"published":"2000-02-04"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2001-0944","kev_date_added":null,"published":"2002-02-02"},{"cvss_score":5,"headline":"Memory corruption in n/a","id":"CVE-2003-1512","kev_date_added":null,"published":"2007-10-25"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2002-0425","kev_date_added":null,"published":"2003-04-02"}],"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":"Local users can execute arbitrary code via a buffer overflow in mIRC's DCC Get Folder Dialog, though the vendor disputes this as a security vulnerability.","url":"https://insights.sbomify.com/CVE-2005-4681/"}