CVE-2024-44191 json
This issue was addressed through improved state management.
published 2024-09-16 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-40940
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
This issue was addressed through improved state management. This issue is fixed in Xcode 16, iOS 17.7 and iPadOS 17.7, iOS 18 and iPadOS 18, macOS Sequoia 15, tvOS 18, visionOS 2, watchOS 11. An app may gain unauthorized access to Bluetooth.
Patch / fix
- Apple Xcode 16
- Apple iOS and iPadOS 17.7, 18
- Apple macOS 15
- Apple tvOS 18
- Apple visionOS 2
- Apple watchOS 11
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Apple Xcode
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
References
-
support.apple.com
/en-us/121238
release-notes, vendor-advisory
-
support.apple.com
/en-us/121239
release-notes, vendor-advisory
-
support.apple.com
/en-us/121240
release-notes, vendor-advisory
-
support.apple.com
/en-us/121246
release-notes, vendor-advisory
-
support.apple.com
/en-us/121248
release-notes, vendor-advisory
-
support.apple.com
/en-us/121249
release-notes, vendor-advisory
-
support.apple.com
/en-us/121250
release-notes, vendor-advisory
- seclists.org /fulldisclosure/2024/Sep/39
- seclists.org /fulldisclosure/2024/Sep/36
- seclists.org /fulldisclosure/2024/Sep/33
- seclists.org /fulldisclosure/2024/Sep/32
Sources
- CVE List CVE-2024-44191
- NVD CVE-2024-44191
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.