{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31976 exists.","fix":"No fix has been published for CVE-2023-31976 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31976 is a high-severity memory corruption vulnerability in Libming Libming, published on 9 May 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-31976 and fix it if it is affected.\n\nWhat it is: CVE-2023-31976 is a high-severity memory corruption vulnerability in Libming Libming, published on 9 May 2023. An attacker can exploit it over the internet without logging in, 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-31976 exists.\n\nAffected product: Libming Libming. 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-31976/ (Markdown: https://insights.sbomify.com/CVE-2023-31976/index.md)","id":"CVE-2023-31976","markdown":"https://insights.sbomify.com/CVE-2023-31976/index.md","name":"CVE-2023-31976","record":{"aliases":["GHSA-cwfh-hr9q-4ghh","UBUNTU-CVE-2023-31976"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libming library","requires_auth":"none","summary":"A stack buffer overflow in libming allows attackers to execute arbitrary code or cause denial of service via crafted input.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libming","vendor":"libming"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"libming v0.4.8 was discovered to contain a stack buffer overflow via the function makeswf_preprocess at /util/makeswf_utils.c.","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-31976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libming:libming","products":["libming:libming"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-31979"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2023-31975"},"products":["n/a"],"published":"2023-05-09","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-50628","kev_date_added":null,"published":"2023-12-20"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-11894","kev_date_added":null,"published":"2020-04-19"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-11895","kev_date_added":null,"published":"2020-04-19"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2019-16705","kev_date_added":null,"published":"2019-09-23"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2023-36239","kev_date_added":null,"published":"2023-06-22"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2020-6628","kev_date_added":null,"published":"2020-01-09"}],"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":"2025-01-29","vendors":["n/a"]},"summary":"A stack buffer overflow in libming allows attackers to execute arbitrary code or cause denial of service via crafted input.","url":"https://insights.sbomify.com/CVE-2023-31976/"}