{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29583 exists.","fix":"No fix has been published for CVE-2023-29583 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-29583 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, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-29583 and fix it if it is affected.\n\nWhat it is: CVE-2023-29583 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, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29583 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-2023-29583/ (Markdown: https://insights.sbomify.com/CVE-2023-29583/index.md)","id":"CVE-2023-29583","markdown":"https://insights.sbomify.com/CVE-2023-29583/index.md","name":"CVE-2023-29583","record":{"aliases":["DEBIAN-CVE-2023-29583","GHSA-x39w-h9m5-w57p"],"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 malformed input, though its security impact is disputed.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yasm","vendor":"yasm_project"}],"cvss":{"score":6.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"yasm 1.3.0.55.g101bc was discovered to contain a stack overflow via the function parse_expr5 at /nasm/nasm-parse.c. 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":"weaponised"},"has_fix":false,"headline":"Memory corruption in n/a","id":"CVE-2023-29583","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":"Memory corruption in n/a","id":"CVE-2023-29584"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-29582"},"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":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":"no","exploitation":"poc","technical_impact":"partial"},"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 malformed input, though its security impact is disputed.","url":"https://insights.sbomify.com/CVE-2023-29583/"}