macOSOperating system · Apple

CVE-2024-44165

HIGH · 7.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 2.0 / 13.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A logic issue was addressed with improved checks. This issue is fixed in iOS 17.7 and iPadOS 17.7, iOS 18 and iPadOS 18, macOS Sequoia 15, macOS Sonoma 14.7, macOS Ventura 13.7, visionOS 2. Network traffic may leak outside a VPN tunnel.

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 · high confidence

A logic flaw in Apple's VPN implementation allows network traffic to bypass the encrypted VPN tunnel, potentially exposing sensitive communications to eavesdropping or interception. The vulnerability stems from insufficient checks in the VPN tunnel handling code, causing traffic to be routed outside the protected tunnel.

MitigationApply the vendor-supplied patches: iOS 17.7 and later, iOS 18 and later, iPadOS 17.7 and later, iPadOS 18 and later, macOS Ventura 13.7 and later, macOS Sonoma 14.7 and later, macOS Sequoia 15 and later, or visionOS 2 and later.

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
macOSOperating system
Affected:< 13.7>= 14.0, < 14.7
Iphone OsOperating system
Affected:< 17.7
IpadosOperating system
Affected:< 17.7
VisionosOperating system
Affected:< 2.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Determine the installed macOS version
    Go to Apple menu > About This Mac. Note the version number shown (e.g., 14.5, 13.6).
    Affected if The version is less than 13.7, or greater than or equal to 14.0 but less than 14.7.
  2. Determine the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About. Note the iOS version number shown (e.g., 17.6).
    Affected if The version is less than 17.7.
  3. Determine the installed visionOS version
    Go to Settings > General > About on Apple Vision Pro. Note the version number shown.
    Affected if The version is less than 2.0.
  4. Check if a VPN profile is configured
    On macOS, go to System Settings > Network > VPN. On iOS/iPadOS, go to Settings > VPN. Look for any VPN configuration profiles listed.
    Affected if A VPN configuration exists on the device.
  5. Verify if VPN is currently connected
    Check the VPN status in the menu bar (macOS) or status indicator in Settings > VPN (iOS/iPadOS). Note whether the VPN shows as Connected.
    Affected if The VPN is actively connected while the device runs an affected OS version.

The device is affected if the installed OS version falls within the affected ranges (macOS < 13.7 or 14.0 <= version < 14.7; iOS/iPadOS < 17.7; visionOS < 2.0) AND a VPN configuration is present or active.

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 / 13.7 / 14.7 or later
Fixed in 2.013.714.7
Interim mitigation

Apply the vendor-supplied patches: iOS 17.7 and later, iOS 18 and later, iPadOS 17.7 and later, iPadOS 18 and later, macOS Ventura 13.7 and later, macOS Sonoma 14.7 and later, macOS Sequoia 15 and later, or visionOS 2 and later.

Recommended fix High confidence

macOS Ventura 13.7, macOS Sonoma 14.7, macOS Sequoia 15, iOS 17.7, iPadOS 17.7, iOS 18, iPadOS 18, visionOS 2.0

  1. Identify your current operating system version on the device (Settings > General > About on iOS/iPadOS/visionOS, System Settings > General > About on macOS)
  2. For macOS Ventura 13.x users: Update to macOS Ventura 13.7 via System Settings > Software Update
  3. For macOS Sonoma 14.x users: Update to macOS Sonoma 14.7 via System Settings > Software Update
  4. For macOS Sequoia 15.x users: Update to macOS Sequoia 15 via System Settings > Software Update
  5. For iPhone/iPad running iOS/iPadOS 17.x: Update to iOS 17.7 or iPadOS 17.7 via Settings > General > Software Update
  6. For iPhone/iPad running iOS/iPadOS 18.x: Update to iOS 18 or iPadOS 18 via Settings > General > Software Update
  7. For Apple Vision Pro users: Update to visionOS 2.0 via Settings > General > Software Update
  8. After updating, verify the VPN connection functions correctly and traffic remains within the tunnel
Caveat Standard Apple point releases typically include security fixes without major breaking changes; however, some third-party VPN clients may require updates for full compatibility

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-44165 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