{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29581 exists.","fix":"No fix has been published for CVE-2023-29581 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-29581 is a medium-severity vulnerability in n/a, published on 12 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-29581 and fix it if it is affected.\n\nWhat it is: CVE-2023-29581 is a medium-severity vulnerability in n/a, published on 12 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-29581 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-29581/ (Markdown: https://insights.sbomify.com/CVE-2023-29581/index.md)","id":"CVE-2023-29581","markdown":"https://insights.sbomify.com/CVE-2023-29581/index.md","name":"CVE-2023-29581","record":{"aliases":["AZL-26166","AZL-35387","DEBIAN-CVE-2023-29581","GHSA-fcm2-5r3h-4j86"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yasm assembler library","requires_auth":"none","summary":"A segmentation violation in the Yasm library can cause applications using it to crash, resulting in a denial of service.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yasm","vendor":"yasm_project"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"yasm 1.3.0.55.g101bc has a segmentation violation in the function delete_Token at modules/preprocs/nasm/nasm-pp.c. NOTE: although a libyasm application could become unavailable if this were exploited, the vendor's position is that there is no security relevance because there is either supposed to be input validation before data reaches libyasm, or a sandbox in which the application runs.","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":"Null dereference in n/a","id":"CVE-2023-29581","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-29582"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2023-29580"},"products":["n/a"],"published":"2023-04-12","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":"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 segmentation violation in the Yasm library can cause applications using it to crash, resulting in a denial of service.","url":"https://insights.sbomify.com/CVE-2023-29581/"}