{"answers":{"affected":"3 open source packages ship an affected version, including libosdp.","exploited":"There is no known exploitation of CVE-2024-52296 in the wild and no public exploit code.","fix":"Upgrade libosdp to 2.4.0 or later.","what":"CVE-2024-52296 is a medium-severity vulnerability in goToMain libosdp, published on 12 Nov 2024. 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-2024-52296 and fix it if it is affected.\n\nWhat it is: CVE-2024-52296 is a medium-severity vulnerability in goToMain libosdp, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-52296 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libosdp (PyPI): affected all versions; fixed in 2.4.0\n- libosdp (PyPI): affected all versions; fixed in 2.4.0\n- libosdp (PyPI): affected all versions; fixed in 2.4.0\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-2024-52296/ (Markdown: https://insights.sbomify.com/CVE-2024-52296/index.md)","id":"CVE-2024-52296","markdown":"https://insights.sbomify.com/CVE-2024-52296/index.md","name":"CVE-2024-52296","record":{"aliases":["GHSA-7945-5mcv-f2pp","PYSEC-2026-1534"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OSDP protocol library","requires_auth":"none","summary":"An attacker can cause a denial of service in libosdp by triggering a null pointer dereference in the osdp_reply_name function.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"libosdp is an implementation of IEC 60839-11-5 OSDP (Open Supervised Device Protocol) and provides a C library with support for C++, Rust and Python3. At ospd_common.c, on the osdp_reply_name function, any reply id between REPLY_ACK and REPLY_XRD is valid, but names array do not declare all of the range. On a case of an undefined reply id within the range, name will be null (name = names[reply_id - REPLY_ACK];). Null name will casue a crash on next line: if (name[0] == '\\0') as null[0] is invalid. As this logic is not limited to a secure connection, attacker may trigger this vulnerability without any prior knowledge. This issue is fixed in 2.4.0.","ecosystems":["PyPI"],"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":"libosdp has a null pointer deref in osdp_reply_name","id":"CVE-2024-52296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"null_dereference","year":"2024"},"n_packages":3,"n_references":2,"next":{"headline":"Tolgee's configuration all configuration properties leaked in public configuration DTO","id":"CVE-2024-52297"},"packages":[{"ecosystem":"PyPI","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"libosdp","purl":null,"source":"GHSA-7945-5mcv-f2pp"},{"ecosystem":"PyPI","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"libosdp","purl":"pkg:pypi/libosdp","source":"GHSA-7945-5mcv-f2pp"},{"ecosystem":"PyPI","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"libosdp","purl":"pkg:pypi/libosdp","source":"PYSEC-2026-1534"}],"prev":{"headline":"DataEase has a forged JWT token vulnerability","id":"CVE-2024-52295"},"products":["libosdp"],"published":"2024-11-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-19","vendors":["goToMain"]},"summary":"An attacker can cause a denial of service in libosdp by triggering a null pointer dereference in the osdp_reply_name function.","url":"https://insights.sbomify.com/CVE-2024-52296/"}