dbcve.org
macOSOperating system · Apple

CVE-2024-27827

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 13.6.7 / 14.5 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 macOS Sonoma 14.5, macOS Ventura 13.6.7. An app may be able to read arbitrary files.

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 local application vulnerability in macOS allows an app to read arbitrary files on the system due to improper state management. This is a moderate-severity (CVSS 5.5) flaw affecting macOS Sonoma prior to 14.5 and macOS Ventura prior to 13.6.7.

MitigationApply the macOS security updates: update macOS Sonoma to 14.5 or later, or macOS Ventura to 13.6.7 or 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.0, < 13.6.7>= 14.0, < 14.5

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the installed macOS version
    Open Terminal and run: sw_vers -productVersion
    Affected if The version displayed is 13.0 to 13.6.6 (Ventura) or 14.0 to 14.4.x (Sonoma)
  2. Confirm the macOS release name
    Run: sw_vers -productVersionExtra (if available) or check System Settings > About to see if it says Ventura or Sonoma
    Affected if The system is running Ventura or Sonoma and the version falls in the vulnerable range

If macOS Ventura is below 13.6.7 or macOS Sonoma is below 14.5, the environment is affected by this arbitrary file read vulnerability.

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.6.7 / 14.5 or later
Fixed in 13.6.714.5
Interim mitigation

Apply the macOS security updates: update macOS Sonoma to 14.5 or later, or macOS Ventura to 13.6.7 or later.

Recommended fix High confidence

macOS 14.5 (for 14.x) or macOS 13.6.7 (for 13.x)

  1. Identify the current macOS version by clicking the Apple menu and selecting About This Mac
  2. If running macOS 14.0-14.4 (Sonoma), plan to upgrade to macOS 14.5
  3. If running macOS 13.0-13.6.6 (Ventura), plan to upgrade to macOS 13.6.7
  4. Back up critical data using Time Machine or another backup solution before performing the update
  5. Open System Settings and navigate to General > Software Update to check for and install the available update
  6. Restart the Mac if prompted to complete the installation
  7. After updating, verify the new version by checking About This Mac to confirm the fix is applied

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

Fix this in macOS 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-27827 — 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-27827 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