# CVE-2024-53980: Spoofed length byte traps CC2538 in endless loop - **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Fix available:** No - **Published:** 29 Nov 2024 - **Updated:** 2 Dec 2024 - **Also known as:** GHSA-m75q-8vj8-wppw ## What is CVE-2024-53980? CVE-2024-53980 is a medium-severity vulnerability in RIOT-OS RIOT, published on 29 Nov 2024. ### Official description RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A malicious actor can send a IEEE 802.15.4 packet with spoofed length byte and optionally spoofed FCS, which eventually results into an endless loop on a CC2538 as receiver. Before PR #20998, the receiver would check for the location of the CRC bit using the packet length byte by considering all 8 bits, instead of discarding bit 7, which is what the radio does. This then results into reading outside of the RX FIFO. Although it prints an error when attempting to read outside of the RX FIFO, it will continue doing this. This may lead to a discrepancy in the CRC check according to the firmware and the radio. If the CPU judges the CRC as correct and the radio is set to `AUTO_ACK`, when the packet requests and acknowledgment the CPU will go into the state `CC2538_STATE_TX_ACK`. However, if the radio judged the CRC as incorrect, it will not send an acknowledgment, and thus the `TXACKDONE` event will not fire. It will then never return to the state `CC2538_STATE_READY` since the baseband processing is still disabled. Then the CPU will be in an endless loop. Since setting to idle is not forced, it won't do it if the radio's state is not `CC2538_STATE_READY`. A fix has not yet been made. Weakness: CWE-835 (Loop with Unreachable Exit Condition) ## Which versions are affected by CVE-2024-53980? It affects 1 product. Products: Riot-Os Riot. ## How do I fix CVE-2024-53980? No fix has been published for CVE-2024-53980 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-53980 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53980 exists. ## Other vulnerabilities in RIOT-OS RIOT - [CVE-2024-32017](https://insights.sbomify.com/CVE-2024-32017/): Buffer overflows in RIOT (critical 9.8) - [CVE-2023-33975](https://insights.sbomify.com/CVE-2023-33975/): RIOT-OS vulnerable to Out of Bounds Write in _rbuf_add (critical 9.8) - [CVE-2023-24819](https://insights.sbomify.com/CVE-2023-24819/): RIOT-OS vulnerable to Buffer Overflow during IPHC receive (critical 9.8) - [CVE-2023-24823](https://insights.sbomify.com/CVE-2023-24823/): RIOT-OS vulnerable to Packet Type Confusion during IPHC send (critical 9.8) - [CVE-2021-27357](https://insights.sbomify.com/CVE-2021-27357/): Memory corruption in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-53980 and fix it if it is affected. What it is: CVE-2024-53980 is a medium-severity vulnerability in RIOT-OS RIOT, published on 29 Nov 2024. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53980 exists. Affected product: RIOT-OS RIOT. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-53980/ (Markdown: https://insights.sbomify.com/CVE-2024-53980/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53980 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53980 - OSV: https://osv.dev/vulnerability/CVE-2024-53980 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-53980/ Summaries are generated and may contain mistakes; the official description above is the record.