cve-2024-52296
Vulnerability from cvelistv5
Published
2024-11-12 15:58
Modified
2024-11-19 17:01
Severity ?
EPSS score ?
Summary
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.
References
{ containers: { adp: [ { metrics: [ { other: { content: { id: "CVE-2024-52296", options: [ { Exploitation: "none", }, { Automatable: "no", }, { "Technical Impact": "partial", }, ], role: "CISA Coordinator", timestamp: "2024-11-19T17:01:45.739953Z", version: "2.0.3", }, type: "ssvc", }, }, ], providerMetadata: { dateUpdated: "2024-11-19T17:01:59.287Z", orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0", shortName: "CISA-ADP", }, title: "CISA ADP Vulnrichment", }, ], cna: { affected: [ { product: "libosdp", vendor: "goToMain", versions: [ { status: "affected", version: "< 2.4.0", }, ], }, ], 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.", }, ], metrics: [ { cvssV3_1: { attackComplexity: "LOW", attackVector: "ADJACENT_NETWORK", availabilityImpact: "HIGH", baseScore: 6.5, baseSeverity: "MEDIUM", confidentialityImpact: "NONE", integrityImpact: "NONE", privilegesRequired: "NONE", scope: "UNCHANGED", userInteraction: "NONE", vectorString: "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", version: "3.1", }, }, ], problemTypes: [ { descriptions: [ { cweId: "CWE-476", description: "CWE-476: NULL Pointer Dereference", lang: "en", type: "CWE", }, ], }, ], providerMetadata: { dateUpdated: "2024-11-12T15:58:28.434Z", orgId: "a0819718-46f1-4df5-94e2-005712e83aaa", shortName: "GitHub_M", }, references: [ { name: "https://github.com/goToMain/libosdp/security/advisories/GHSA-7945-5mcv-f2pp", tags: [ "x_refsource_CONFIRM", ], url: "https://github.com/goToMain/libosdp/security/advisories/GHSA-7945-5mcv-f2pp", }, { name: "https://github.com/goToMain/libosdp/commit/24409e98a260176765956ec766a04cb35984fab1", tags: [ "x_refsource_MISC", ], url: "https://github.com/goToMain/libosdp/commit/24409e98a260176765956ec766a04cb35984fab1", }, ], source: { advisory: "GHSA-7945-5mcv-f2pp", discovery: "UNKNOWN", }, title: "libosdp has a null pointer deref in osdp_reply_name", }, }, cveMetadata: { assignerOrgId: "a0819718-46f1-4df5-94e2-005712e83aaa", assignerShortName: "GitHub_M", cveId: "CVE-2024-52296", datePublished: "2024-11-12T15:58:28.434Z", dateReserved: "2024-11-06T19:00:26.395Z", dateUpdated: "2024-11-19T17:01:59.287Z", state: "PUBLISHED", }, dataType: "CVE_RECORD", dataVersion: "5.1", "vulnerability-lookup:meta": { fkie_nvd: { 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.\"}]", id: "CVE-2024-52296", lastModified: "2024-11-13T17:01:58.603", metrics: "{\"cvssMetricV31\": [{\"source\": \"security-advisories@github.com\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\", \"baseScore\": 6.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"ADJACENT_NETWORK\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"NONE\", \"userInteraction\": \"NONE\", \"scope\": \"UNCHANGED\", \"confidentialityImpact\": \"NONE\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"HIGH\"}, \"exploitabilityScore\": 2.8, \"impactScore\": 3.6}]}", 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\"}]", sourceIdentifier: "security-advisories@github.com", vulnStatus: "Awaiting Analysis", weaknesses: "[{\"source\": \"security-advisories@github.com\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-476\"}]}]", }, nvd: "{\"cve\":{\"id\":\"CVE-2024-52296\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2024-11-12T16:15:26.030\",\"lastModified\":\"2024-11-13T17:01:58.603\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"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ón de IEC 60839-11-5 OSDP (Open Supervised Device Protocol) y proporciona una librería C con soporte para C++, Rust y Python3. En ospd_common.c, en la función osdp_reply_name, cualquier id de respuesta entre REPLY_ACK y REPLY_XRD es válido, 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á nulo (nombre = nombres[id_de_respuesta - REPLY_ACK];). Un nombre nulo provocará un bloqueo en la siguiente línea: si (nombre[0] == '\\\\0') ya que null[0] no es válido. Como esta lógica no se limita a una conexión segura, el atacante puede activar esta vulnerabilidad sin ningún conocimiento previo. Este problema se solucionó en 2.4.0.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"ADJACENT_NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":2.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-476\"}]}],\"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\"}]}}", vulnrichment: { containers: "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-52296\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-11-19T17:01:45.739953Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-11-19T17:01:54.480Z\"}}], \"cna\": {\"title\": \"libosdp has a null pointer deref in osdp_reply_name\", \"source\": {\"advisory\": \"GHSA-7945-5mcv-f2pp\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"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\"}}], \"affected\": [{\"vendor\": \"goToMain\", \"product\": \"libosdp\", \"versions\": [{\"status\": \"affected\", \"version\": \"< 2.4.0\"}]}], \"references\": [{\"url\": \"https://github.com/goToMain/libosdp/security/advisories/GHSA-7945-5mcv-f2pp\", \"name\": \"https://github.com/goToMain/libosdp/security/advisories/GHSA-7945-5mcv-f2pp\", \"tags\": [\"x_refsource_CONFIRM\"]}, {\"url\": \"https://github.com/goToMain/libosdp/commit/24409e98a260176765956ec766a04cb35984fab1\", \"name\": \"https://github.com/goToMain/libosdp/commit/24409e98a260176765956ec766a04cb35984fab1\", \"tags\": [\"x_refsource_MISC\"]}], \"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.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-476\", \"description\": \"CWE-476: NULL Pointer Dereference\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2024-11-12T15:58:28.434Z\"}}}", cveMetadata: "{\"cveId\": \"CVE-2024-52296\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-11-19T17:01:59.287Z\", \"dateReserved\": \"2024-11-06T19:00:26.395Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2024-11-12T15:58:28.434Z\", \"assignerShortName\": \"GitHub_M\"}", dataType: "CVE_RECORD", dataVersion: "5.1", }, }, }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.