CVE-2024-32018

{"id": "CVE-2024-32018", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}, {"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 2.2}]}, "published": "2024-05-01T07:15:39.590", "references": [{"url": "http://seclists.org/fulldisclosure/2024/May/7", "tags": ["Mailing List", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "http://www.openwall.com/lists/oss-security/2024/05/07/3", "tags": ["Mailing List", "Third Party Advisory"], "source": "security-advisories@github.com"}, {"url": "https://github.com/RIOT-OS/RIOT/blob/master/pkg/nimble/scanlist/nimble_scanlist.c#L74-L87", "tags": ["Product"], "source": "security-advisories@github.com"}, {"url": "https://github.com/RIOT-OS/RIOT/security/advisories/GHSA-899m-q6pp-hmp3", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "http://seclists.org/fulldisclosure/2024/May/7", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "http://www.openwall.com/lists/oss-security/2024/05/07/3", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/RIOT-OS/RIOT/blob/master/pkg/nimble/scanlist/nimble_scanlist.c#L74-L87", "tags": ["Product"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://github.com/RIOT-OS/RIOT/security/advisories/GHSA-899m-q6pp-hmp3", "tags": ["Exploit", "Vendor Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-120"}]}], "descriptions": [{"lang": "en", "value": "RIOT is a real-time multi-threading operating system that supports a range of devices that are typically 8-bit, 16-bit and 32-bit microcontrollers. Most codebases define assertion macros which compile to a no-op on non-debug builds. If assertions are the only line of defense against untrusted input, the software may be exposed to attacks that leverage the lack of proper input checks. In detail, in the `nimble_scanlist_update()` function below, `len` is checked in an assertion and subsequently used in a call to `memcpy()`. If an attacker is able to provide a larger `len` value while assertions are compiled-out, they can write past the end of the fixed-length `e->ad` buffer. If the unchecked input above is attacker-controlled and crosses a security boundary, the impact of the buffer overflow vulnerability could range from denial of service to arbitrary code execution. This issue has not yet been patched. Users are advised to add manual `len` checking."}, {"lang": "es", "value": "RIOT es un sistema operativo multiproceso en tiempo real que admite una variedad de dispositivos que suelen ser microcontroladores de 8, 16 y 32 bits. La mayor\u00eda de las bases de c\u00f3digo definen macros de aserci\u00f3n que se compilan sin operaci\u00f3n en compilaciones que no son de depuraci\u00f3n. Si las afirmaciones son la \u00fanica l\u00ednea de defensa contra entradas que no son de confianza, el software puede quedar expuesto a ataques que aprovechen la falta de comprobaciones de entrada adecuadas. En detalle, en la funci\u00f3n `nimble_scanlist_update()` siguiente, `len` se verifica en una aserci\u00f3n y posteriormente se usa en una llamada a `memcpy()`. Si un atacante puede proporcionar un valor `len` mayor mientras se compilan las afirmaciones, puede escribir m\u00e1s all\u00e1 del final del b\u00fafer `e->ad` de longitud fija. Si la entrada no verificada anterior est\u00e1 controlada por un atacante y cruza un l\u00edmite de seguridad, el impacto de la vulnerabilidad de desbordamiento del b\u00fafer podr\u00eda variar desde denegaci\u00f3n de servicio hasta ejecuci\u00f3n de c\u00f3digo arbitrario. Este problema a\u00fan no se ha solucionado. Se recomienda a los usuarios que agreguen la verificaci\u00f3n manual de \"len\"."}], "lastModified": "2025-09-05T13:17:46.793", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:riot-os:riot:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "2817153B-248F-4852-9999-DA4891E5EB30", "versionEndIncluding": "2024.01"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}