dbcve.org
XcodeApplication · Apple

CVE-2024-44191

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 2.0 / 11.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A state management flaw in Apple operating systems allows a malicious or misconfigured application to bypass Bluetooth authorization checks and gain unauthorized access to Bluetooth functionality. The vulnerability stems from improper validation of the Bluetooth state/authorization before permitting access.

MitigationUpdate affected Apple devices to iOS 17.7/18+, iPadOS 17.7/18+, macOS Sequoia 15+, tvOS 18+, visionOS 2+, or watchOS 11+ as appropriate. For internal applications, ensure Bluetooth permission requests properly handle authorization state transitions and validate permissions at runtime.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XcodeApplication
Affected:< 16.0
IpadosOperating system
Affected:< 17.7
Iphone OsOperating system
Affected:< 17.7
macOSOperating system
Affected:< 15.0
TvosOperating system
Affected:< 18.0
VisionosOperating system
Affected:< 2.0
WatchosOperating system
Affected:< 11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version
    Go to Settings > General > About on the iPhone or iPad. Look for the 'Version' field (e.g., 17.6.1).
    Affected if Version is less than 17.7 (e.g., 17.0 through 17.6.x)
  2. Check iPadOS version
    Go to Settings > General > About on the iPad. Note the version number displayed.
    Affected if Version is less than 17.7
  3. Check macOS version
    Click Apple menu > About This Mac. The version number appears below the macOS name (e.g., 14.5).
    Affected if Version is less than 15.0 (versions 14.x and earlier are affected)
  4. Check tvOS version
    Go to Settings > General > About TV on Apple TV. The version is shown next to 'Version'.
    Affected if Version is less than 18.0
  5. Check watchOS version
    Open the Watch app on iPhone, go to My Watch > General > About. Note the watchOS version.
    Affected if Version is less than 11.0
  6. Check visionOS version
    Go to Settings > General > About on Apple Vision Pro. Record the version number shown.
    Affected if Version is less than 2.0

Your device is affected if it runs any version below the fixed release for its platform (iOS/iPadOS 17.7+, macOS 15+, tvOS 18+, watchOS 11+, visionOS 2+).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0 / 11.0 / 15.0 or later
Fixed in 2.011.015.0
Interim mitigation

Update affected Apple devices to iOS 17.7/18+, iPadOS 17.7/18+, macOS Sequoia 15+, tvOS 18+, visionOS 2+, or watchOS 11+ as appropriate. For internal applications, ensure Bluetooth permission requests properly handle authorization state transitions and validate permissions at runtime.

Recommended fix High confidence

Xcode 16; iOS 17.7/iPadOS 17.7 or iOS 18/iPadOS 18; macOS Sequoia 15; tvOS 18; visionOS 2; watchOS 11

  1. Identify the affected Apple product(s) from the list: Xcode, iPadOS, iPhone OS, macOS, tvOS, visionOS, or watchOS
  2. For Xcode: upgrade to version 16.0 or later
  3. For iPhone and iPad: upgrade to iOS 17.7/iPadOS 17.7, or iOS 18/iPadOS 18
  4. For Mac: upgrade to macOS Sequoia 15.0 or later
  5. For Apple TV: upgrade to tvOS 18.0 or later
  6. For Apple Vision Pro: upgrade to visionOS 2.0 or later
  7. For Apple Watch: upgrade to watchOS 11.0 or later
Caveat Apple OS upgrades may introduce app compatibility issues or remove support for older devices; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xcode Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44191 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data