VulnerabilityPublished 20 Nov 2024Updated 25 Nov 2024

CVE-2024-48982: mbed-os · Classic Buffer Overflow

Affects mbed-osSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubmbed-ce/mbed-os`pkg:github/mbed-ce/mbed-os`Other threats	Affected =6.16.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-48982, organizations should first monitor for any patches or updates from the MBed OS maintainers and apply them promptly once available. In the absence of patches, network-level controls should be implemented to restrict or filter incoming HCI packets from untrusted sources, especially on wireless interfaces. Deploying intrusion detection or prevention systems capable of recognizing malformed HCI packets can help detect exploitation attempts. Device firmware should be updated to include additional input validation checks on HCI packet lengths to enforce minimum length constraints and prevent integer overflows. Where feasible, isolate MBed OS devices on segmented networks to limit exposure. Conduct thorough testing of device resilience against malformed packets in controlled environments. Finally, maintain robust incident response plans to quickly address any denial of service incidents related to this vulnerability.

Description

An issue was discovered in MBed OS 6.16.0. Its hci parsing software dynamically determines the length of certain hci packets by reading a byte from its header. This value is assumed to be greater than or equal to 3, but the software doesn't ensure that this is the case. Supplying a length less than 3 leads to a buffer overflow in a buffer that is allocated later. It is simultaneously possible to cause another integer overflow by supplying large length values because the provided length value is increased by a few bytes to account for additional information that is supposed to be stored there. This bug is trivial to exploit for a denial of service but is not certain to suffice to bring the system down and can generally not be exploited further because the exploitable buffer is dynamically allocated.

Impact

The primary impact of CVE-2024-48982 is denial of service (DoS) through system crashes caused by buffer overflow and integer overflow conditions in MBed OS 6.16.0. Devices relying on MBed OS for Bluetooth or wireless communication may become unresponsive or reboot unexpectedly when processing maliciously crafted HCI packets. This can disrupt critical IoT, embedded, or industrial control systems, potentially affecting operational continuity. Although the vulnerability does not appear to allow remote code execution or data compromise, the loss of availability can have significant consequences in environments where uptime and reliability are critical, such as healthcare devices, smart infrastructure, and industrial automation. The ease of remote exploitation without authentication or user interaction increases the risk of widespread attacks, especially in environments with exposed wireless interfaces. Organizations deploying MBed OS-based devices should consider the risk of service disruption and potential cascading effects on dependent systems.

Summary

CVE-2024-48982 affects MBed OS version 6.16.0, specifically its Host Controller Interface (HCI) packet parsing component. The vulnerability stems from improper validation of the length field in certain HCI packets. The software expects the length byte to be at least 3, but does not enforce this constraint. If an attacker supplies a length less than 3, a buffer overflow occurs in a buffer allocated later in the parsing process. This can lead to memory corruption and potential denial of service. Furthermore, the length value is incremented by a fixed number of bytes to accommodate additional data, which can cause an integer overflow if the length is large enough. This integer overflow can result in an incorrectly sized buffer allocation, further exacerbating the risk of memory corruption. The vulnerability is classified under CWE-120 (Classic Buffer Overflow). Exploitation requires no privileges or user interaction and can be performed remotely over the network interface. While the vulnerability is trivial to exploit for denial of service, the dynamic allocation of the buffer limits the likelihood of more severe impacts such as code execution. No patches have been published yet, and no active exploits are known. This vulnerability primarily affects devices running MBed OS 6.16.0 that handle Bluetooth or other wireless communications using HCI packets.

CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #11
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.1 (opens in a new tab)
V14.1.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 21:49 UTC

WeaknessesCWE-120

Technical details

References

Community reviews

Related threats