CVE-2024-52296

{"id": "CVE-2024-52296", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "ADJACENT_NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "published": "2024-11-12T16:15:26.030", "references": [{"url": "https://github.com/goToMain/libosdp/commit/24409e98a260176765956ec766a04cb35984fab1", "source": "security-advisories@github.com"}, {"url": "https://github.com/goToMain/libosdp/security/advisories/GHSA-7945-5mcv-f2pp", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-476"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "libosdp es una implementaci\u00f3n de IEC 60839-11-5 OSDP (Open Supervised Device Protocol) y proporciona una librer\u00eda C con soporte para C++, Rust y Python3. En ospd_common.c, en la funci\u00f3n osdp_reply_name, cualquier id de respuesta entre REPLY_ACK y REPLY_XRD es v\u00e1lido, pero la matriz de nombres no declara todo el rango. En el caso de un id de respuesta indefinido dentro del rango, el nombre ser\u00e1 nulo (nombre = nombres[id_de_respuesta - REPLY_ACK];). Un nombre nulo provocar\u00e1 un bloqueo en la siguiente l\u00ednea: si (nombre[0] == '\\0') ya que null[0] no es v\u00e1lido. Como esta l\u00f3gica no se limita a una conexi\u00f3n segura, el atacante puede activar esta vulnerabilidad sin ning\u00fan conocimiento previo. Este problema se solucion\u00f3 en 2.4.0."}], "lastModified": "2024-11-13T17:01:58.603", "sourceIdentifier": "security-advisories@github.com"}