{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-29579 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2023-29579 is a medium-severity memory corruption vulnerability in n/a, published on 24 Apr 2023. 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-2023-29579 and fix it if it is affected.\n\nWhat it is: CVE-2023-29579 is a medium-severity memory corruption vulnerability in n/a, published on 24 Apr 2023. 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-2023-29579 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-2023-29579/ (Markdown: https://insights.sbomify.com/CVE-2023-29579/index.md)","id":"CVE-2023-29579","markdown":"https://insights.sbomify.com/CVE-2023-29579/index.md","name":"CVE-2023-29579","record":{"aliases":["DEBIAN-CVE-2023-29579","GHSA-9rj4-9hjf-7pcg"],"analysis":{"component_type":"developer_tool","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yasm assembler","requires_auth":"none","summary":"A stack overflow in the Yasm assembler can cause a denial of service when processing specific inputs, though its security impact is disputed.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yasm","vendor":"yasm_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"yasm 1.3.0.55.g101bc was discovered to contain a stack overflow via the component yasm/yasm+0x43b466 in vsprintf. Note: This has been disputed by third parties who argue this is a bug and not a security issue because yasm is a standalone program not designed to run untrusted code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2023-29579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2023-29580"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-29578"},"products":["n/a"],"published":"2023-04-24","related":[{"cvss_score":7.8,"headline":"Null dereference in n/a","id":"CVE-2023-31724","kev_date_added":null,"published":"2023-05-17"},{"cvss_score":6.2,"headline":"Memory corruption in n/a","id":"CVE-2023-29583","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":5.5,"headline":"Use after free in n/a","id":"CVE-2023-49554","kev_date_added":null,"published":"2024-01-02"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2023-49555","kev_date_added":null,"published":"2024-01-02"},{"cvss_score":5.5,"headline":"Memory corruption in n/a","id":"CVE-2023-49556","kev_date_added":null,"published":"2024-01-02"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2023-49557","kev_date_added":null,"published":"2024-01-02"},{"cvss_score":5.5,"headline":"Denial of service in n/a","id":"CVE-2023-49558","kev_date_added":null,"published":"2024-01-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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"A stack overflow in the Yasm assembler can cause a denial of service when processing specific inputs, though its security impact is disputed.","url":"https://insights.sbomify.com/CVE-2023-29579/"}