IpadosOperating system · Apple

CVE-2024-27876

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 2.0 / 13.7 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
A race condition was addressed with improved locking. 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. Unpacking a maliciously crafted archive may allow an attacker to write 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 · moderate confidence

Race condition in Apple archive unpacking functionality allows a maliciously crafted archive to write arbitrary files to the filesystem due to improper locking during extraction. The vulnerability enables local privilege escalation or file system manipulation by tricking a user into extracting a specially designed archive.

MitigationApply the available security updates (iOS 17.7/18, iPadOS 17.18, macOS Ventura 13.7/Sonoma 14.7/Sequoia 15, visionOS 2) or avoid unpacking archives from untrusted sources until patches are applied.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 and note the Version number
    Affected if Version is less than 17.7 (e.g., 17.6.x or earlier)
  2. Check iPadOS version
    Go to Settings > General > About and note the Version number
    Affected if Version is less than 17.7 (e.g., 17.6.x or earlier)
  3. Check macOS version
    Click Apple menu > About This Mac and note the version number under macOS
    Affected if Version is 13.0 to 13.6.x OR 14.0 to 14.6.x (falls within the affected ranges)
  4. Check visionOS version
    Go to Settings > General > About and note the Version number
    Affected if Version is less than 2.0 (e.g., 1.x)
  5. Identify archive extraction activity
    Review recently extracted archives in Downloads folder, Desktop, or locations where you extracted .zip, .tar, .rar files from untrusted or unknown sources
    Affected if You have extracted archives from untrusted or unknown sources since the vulnerable versions were released

You are affected if your installed OS version falls within the vulnerable ranges AND you have extracted archives from untrusted sources, as the race condition triggers during the extraction process.

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 available security updates (iOS 17.7/18, iPadOS 17.18, macOS Ventura 13.7/Sonoma 14.7/Sequoia 15, visionOS 2) or avoid unpacking archives from untrusted sources until patches are applied.

Recommended fix High confidence

iOS 17.7/iPadOS 17.7, iOS 18/iPadOS 18, macOS Ventura 13.7, macOS Sonoma 14.7, macOS Sequoia 15, or visionOS 2

  1. For iPhone or iPad users: Go to Settings > General > Software Update and upgrade to iOS 17.7/iPadOS 17.7 or iOS 18/iPadOS 18
  2. For Mac users: Go to System Settings > General > Software Update and upgrade to macOS Ventura 13.7, macOS Sonoma 14.7, or macOS Sequoia 15 depending on your current version
  3. For Vision Pro users: Go to Settings > General > Software Update and upgrade to visionOS 2
  4. After updating, verify the version in Settings to confirm the patch is applied
Caveat Apple point releases typically have minimal breaking changes; however, some older apps may have compatibility issues with major OS upgrades such as iOS 18 or macOS Sequoia

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

Fix this in Ipados Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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