CVE-2024-52296 libosdp has a null pointer deref in osdp_reply_name

Medium 6.5 Published Updated

An attacker can cause a denial of service in libosdp by triggering a null pointer dereference in the osdp_reply_name function.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2024-52296?

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.

Official 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.

Weakness: CWE-476

Which versions are affected by CVE-2024-52296?

3 open source packages ship an affected version, including libosdp.

PackageAffectedFixed in
libosdp PyPIAll versions2.4.0
libosdp PyPIAll versions2.4.0
libosdp PyPIAll versions2.4.0

How do I fix CVE-2024-52296?

Upgrade libosdp to 2.4.0 or later.

Is CVE-2024-52296 being exploited?

There is no known exploitation of CVE-2024-52296 in the wild and no public exploit code.

Sources

Also known as GHSA-7945-5mcv-f2pp, PYSEC-2026-1534.

Is CVE-2024-52296 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free