VulnerabilityPublished 17 Sep 2024Updated 4 Nov 2025

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

Source GCVE Database

Compare

Authoritative record:CVE-2024-44171· Medium 4.6

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

Data as of 4 Nov 2026, 17:20 UTC

CVSS 3.1 base score

4.6Medium

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

Patch: Available – fixed in 17.7

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

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
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: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: 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-jvcj-gmhm-rfx5

What to do

AI-suggested

Apply the official fixes by updating to iOS 17.7, iPadOS 17.7, iOS 18, iPadOS 18, or watchOS 11. These versions include improved state management that addresses the vulnerability. No additional mitigation steps are indicated.

Description

CVE-2024-44171 is a vulnerability affecting iOS and iPadOS devices, as well as watchOS, where an attacker with physical access to a locked device could potentially control nearby devices via accessibility features. The issue is addressed through improved state management and fixed in iOS 17.7, iPadOS 17.7, iOS 18, iPadOS 18, and watchOS 11.

Impact

An attacker with physical access to a locked device could leverage this vulnerability to control nearby devices via accessibility features, potentially leading to unauthorized control or manipulation of those devices. The vulnerability does not impact confidentiality but has a high impact on integrity. There is no indication of availability impact. No known exploits are reported in the wild.

References

Community reviews

Loading reviews…