{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31981 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2023-31981 is a high-severity memory corruption vulnerability in n/a, published on 9 May 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-31981 and fix it if it is affected.\n\nWhat it is: CVE-2023-31981 is a high-severity memory corruption vulnerability in n/a, published on 9 May 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-31981 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-31981/ (Markdown: https://insights.sbomify.com/CVE-2023-31981/index.md)","id":"CVE-2023-31981","markdown":"https://insights.sbomify.com/CVE-2023-31981/index.md","name":"CVE-2023-31981","record":{"aliases":["DEBIAN-CVE-2023-31981","GHSA-27pq-ccjc-wxmc","UBUNTU-CVE-2023-31981"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SIP packet analyzer","requires_auth":"none","summary":"A stack buffer overflow in Sngrep allows attackers to execute arbitrary code or cause a denial of service via crafted packets.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sngrep","vendor":"irontec"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/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":"Sngrep v1.6.0 was discovered to contain a stack buffer overflow via the function packet_set_payload at /src/packet.c.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2023-31981","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-31982"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-31979"},"products":["n/a"],"published":"2023-05-09","related":[{"cvss_score":9,"headline":"Stack-Buffer Overflow in 'Call-ID' and 'X-Call-ID' SIP Header Processing in sngrep","id":"CVE-2024-3119","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":9,"headline":"Stack-Buffer Overflow in 'Content-Length' and 'Warning' Header Processing in sngrep","id":"CVE-2024-3120","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2023-36192","kev_date_added":null,"published":"2023-06-23"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2023-31982","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-35434","kev_date_added":null,"published":"2024-05-29"}],"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 Sngrep allows attackers to execute arbitrary code or cause a denial of service via crafted packets.","url":"https://insights.sbomify.com/CVE-2023-31981/"}