goToMain libosdp up to 2.3.x ospd_common.c osdp_reply_name null pointer dereference

Summaryinfo

A vulnerability was found in goToMain libosdp up to 2.3.x. It has been declared as problematic. This issue affects the function osdp_reply_name of the file ospd_common.c. Such manipulation leads to null pointer dereference. This vulnerability is traded as CVE-2024-52296. Access to the local network is required for this attack to succeed. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in goToMain libosdp up to 2.3.x. Affected by this issue is the function osdp_reply_name of the file ospd_common.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2024-52296 since 11/06/2024. The exploitation is known to be easy. Access to the local network is required for this attack to succeed. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.

Upgrading to version 2.4.0 eliminates this vulnerability. Applying the patch 24409e98a260176765956ec766a04cb35984fab1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• goToMain

Name

• libosdp

Version

• 2.0
• 2.1
• 2.2
• 2.3

License

• open-source

Website

• Product: https://github.com/goToMain/libosdp/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion