{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1679 exists.","fix":"No fix has been published for CVE-2005-1679 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-1679 is a medium-severity memory corruption vulnerability in n/a, published on 25 May 2005."},"fix_prompt":"Check this codebase for CVE-2005-1679 and fix it if it is affected.\n\nWhat it is: CVE-2005-1679 is a medium-severity memory corruption vulnerability in n/a, published on 25 May 2005. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1679 exists.\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-1679/ (Markdown: https://insights.sbomify.com/CVE-2005-1679/index.md)","id":"CVE-2005-1679","markdown":"https://insights.sbomify.com/CVE-2005-1679/index.md","name":"CVE-2005-1679","record":{"aliases":["GHSA-96cm-jr6m-rrfm"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"picasm assembler","requires_auth":"none","summary":"Attackers can execute arbitrary code via a stack-based buffer overflow in the picasm assembler's error directive when processing long error messages.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"picasm","vendor":"timo_rossi"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Stack-based buffer overflow in the error directive in picasm 1.12b and earlier allows attackers to execute arbitrary code via a long error message.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-05-20","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-05-20","kind":"exploitdb","ref":"25687","stars":null,"title":"Picasm 1.10/1.12 - Error Generation Remote Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2005-1679","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-1680"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2005-1678"},"products":["n/a"],"published":"2005-05-25","related":[],"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-07","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via a stack-based buffer overflow in the picasm assembler's error directive when processing long error messages.","url":"https://insights.sbomify.com/CVE-2005-1679/"}