macOSOperating system · Apple

CVE-2024-44289

HIGH · 7.5 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 13.7.1 / 14.7.1 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 privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in macOS Sequoia 15.1, macOS Sonoma 14.7.1, macOS Ventura 13.7.1. An app may be able to read sensitive location information.

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 privacy vulnerability in macOS allowed applications to read sensitive location information from system log entries that were not properly redacted. The issue stemmed from insufficient private data redaction in log handling, potentially exposing location data to unauthorized apps.

MitigationApply the appropriate macOS security update: macOS Sequoia 15.1, macOS Sonoma 14.7.1, or macOS Ventura 13.7.1.

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.1>= 14.0, < 14.7.1

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. Check installed macOS version
    Go to Apple menu > About This Mac > General tab, or run 'sw_vers' in Terminal
    Affected if Version is earlier than 13.7.1, or between 14.0 and 14.7.1, or earlier than 15.1 if on Sequoia
  2. Confirm macOS name and build
    Run 'sw_vers' in Terminal to see version number and marketing name (Ventura, Sonoma, or Sequoia)
    Affected if Running an affected version as defined in the CVE (Ventura <13.7.1, Sonoma >=14.0 and <14.7.1, or Sequoia <15.1)
  3. Check if Location Services are enabled
    Go to System Settings > Privacy & Security > Location Services, or check for locationd process activity
    Affected if Location Services are enabled and the macOS version falls within the affected ranges, as location data could be written to logs
  4. Review system logs for potential location data
    Use Console app or 'log show' command to inspect system logs around the time location services were used
    Affected if Logs contain unaudited location-related entries and the system is on an unpatched macOS version

A user is affected if their macOS version falls within the ranges: <13.7.1 (Ventura), >=14.0 and <14.7.1 (Sonoma), or <15.1 (Sequoia) AND they use Location Services with system logging enabled.

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 13.7.1 / 14.7.1 or later
Fixed in 13.7.114.7.1
Interim mitigation

Apply the appropriate macOS security update: macOS Sequoia 15.1, macOS Sonoma 14.7.1, or macOS Ventura 13.7.1.

Recommended fix High confidence

macOS Ventura 13.7.1 / macOS Sonoma 14.7.1 / macOS Sequoia 15.1 (depending on which macOS major version is currently in use)

  1. Back up important data before performing any system update
  2. Identify the current macOS version by clicking the Apple menu and selecting About This Mac
  3. For macOS Ventura (13.x) users: Install macOS Ventura 13.7.1 security update via System Settings > General > Software Update
  4. For macOS Sonoma (14.x) users: Install macOS Sonoma 14.7.1 security update via System Settings > General > Software Update
  5. For macOS Sequoia (15.x) users: Install macOS Sequoia 15.1 via System Settings > General > Software Update
  6. After updating, verify the update was successful by checking About This Mac to confirm the installed version
Caveat Standard macOS update risks apply - ensure critical data is backed up; some legacy applications may have compatibility issues with newer point releases

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

Fix this in macOS Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44289 — 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-44289 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