CVE-2024-53980: Spoofed length byte traps CC2538 in endless loop
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 AUTOACK, when the packet requests and acknowledgment the CPU will go into the state CC2538STATETXACK. 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 CC2538STATEREADY 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 CC2538STATEREADY. A fix has not yet been made.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53980?
The severity of CVE-2024-53980 has not been explicitly rated, but it poses a risk to the integrity of RIOT OS when processing IEEE 802.15.4 packets.
How do I fix CVE-2024-53980?
To fix CVE-2024-53980, update to the latest version of RIOT OS that addresses this vulnerability.
Who is affected by CVE-2024-53980?
CVE-2024-53980 affects current versions of RIOT OS used in IoT and embedded devices.
What exploit mechanism is described in CVE-2024-53980?
CVE-2024-53980 allows attackers to send a spoofed IEEE 802.15.4 packet which can lead to vulnerabilities in packet processing.
Is there a workaround for CVE-2024-53980?
Currently, no specific workaround is provided for CVE-2024-53980, so updating the software is recommended.