VulnerabilityPublished 17 Sep 2024Updated 4 Nov 2025

CVE-2024-44191: This issue was addressed through improved state management

Source GCVE Database

Compare

Authoritative record:CVE-2024-44191· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium · fixed in 17.7 : update affected systems when convenient.

Data as of 4 Nov 2026, 17:21 UTC

CVSS 3.1 base score

5.5Medium

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

Patch: Available – fixed in 17.7

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 4 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.

ghsa-m6gq-8g82-wvgx

What to do

AI-suggested

The vulnerability is fixed in iOS 17.7, iPadOS 17.7, Xcode 16, visionOS 2, watchOS 11, macOS Sequoia 15, iOS 18, iPadOS 18, and tvOS 18. Users and administrators should apply these updates to remediate the issue. No additional mitigation steps are indicated.

Description

CVE-2024-44191 is a medium severity vulnerability affecting multiple Apple operating systems including iOS, iPadOS, macOS, watchOS, tvOS, visionOS, and Xcode. The flaw allowed an app to gain unauthorized access to Bluetooth functionality. The issue was addressed through improved state management and is fixed in iOS 17.7, iPadOS 17.7, Xcode 16, visionOS 2, watchOS 11, macOS Sequoia 15, iOS 18, iPadOS 18, and tvOS 18.

Impact

An attacker controlling a local app with low privileges could exploit this vulnerability to gain unauthorized access to Bluetooth functionality, potentially allowing manipulation or interference with Bluetooth operations. The impact is limited to integrity, with no direct confidentiality or availability impact reported.

Summary

This vulnerability (CVE-2024-44191) involved improper state management that could allow an application to gain unauthorized access to Bluetooth capabilities on affected Apple platforms. The issue was resolved by Apple through improved state management in the specified fixed versions. The CVSS v3.1 base score is 5.5, indicating a medium severity with local attack vector, low attack complexity, requiring low privileges and no user interaction, impacting integrity but not confidentiality or availability.

References

Community reviews

Loading reviews…