Skip to content

Usage of Uninitialized Timer during forwarding of Fragments with SFR

Moderate
miri64 published GHSA-xfj4-9g7w-f4gh May 30, 2023

Package

RIOT-OS

Affected versions

<= 2022.10

Patched versions

2023.04

Description

Impact

RIOT-OS contains a network stack with the ability to process 6LoWPAN frames. An attacker can send crafted frames to the device to trigger the usage of an uninitialized object leading to denial of service.

Patches

No public patches are available.

Workarounds

  • Disabling fragment forwarding or SFR

For more information

If you have any questions or comments about this advisory:

Bug Details

If SFR is activated the 6LoWPAN stack uses a timer to handle fragment timeouts.
The timer is only initialized once the first fragment with _frag_ack_req is send (source):

    if (_frag_ack_req(frag_desc)) {
        /* initialize _arq_timer if not yet done */
        if (_arq_timer.callback == NULL) {
            evtimer_init_msg(&_arq_timer);
        }
        _sched_arq_timeout(fbuf, fbuf->sfr.arq_timeout);
    }

If an error occurs during processing of this frame the timer won't be initialized but is still used (source).
Once the timer event fires it calls the uninitialized function pointer of the event.
Which then results in a crash.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE ID

CVE-2023-24826

Weaknesses

Credits