dbcve.org
IpadosOperating system · Apple

CVE-2023-32384

HIGH · 7.8 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 9.5 / 11.7.7 or later.
See remediation →
81/100
Remediation priority · High
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 buffer overflow was addressed with improved bounds checking. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.6 and iPadOS 15.7.6, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, iOS 16.5 and iPadOS 16.5. Processing an image may lead to arbitrary code execution.

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 buffer overflow vulnerability in image processing across multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS) allows arbitrary code execution due to insufficient bounds checking when processing specially crafted images.

MitigationUpdate all affected devices to the patched versions: iOS 15.7.6/16.5+, iPadOS 15.7.6/16.5+, macOS Ventura 13.4+, macOS Big Sur 11.7.7+, macOS Monterey 12.6.6+, tvOS 16.5+, and watchOS 9.5+.

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:< 15.7.6>= 16.0, < 16.5
Iphone OsOperating system
Affected:< 15.7.6>= 16.0, < 16.5
macOSOperating system
Affected:>= 11.0.0, < 11.7.7>= 12.0.0, < 12.6.6>= 13.0, < 13.4
TvosOperating system
Affected:< 16.5
WatchosOperating system
Affected:< 9.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
High
Availability
High

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

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 on iPhone
    Go to Settings > General > About > Version
    Affected if version is below 15.7.6 OR version is 16.0 through 16.4.x
  2. Check iPadOS version on iPad
    Go to Settings > General > About > Version
    Affected if version is below 15.7.6 OR version is 16.0 through 16.4.x
  3. Check macOS version
    Click Apple menu > About This Mac
    Affected if version is 11.0.0-11.7.6, 12.0.0-12.6.5, or 13.0-13.3.x
  4. Check tvOS version
    Go to Settings > General > About > Version
    Affected if version is below 16.5
  5. Check watchOS version
    Open Watch app on paired iPhone > My Watch tab > General > About
    Affected if version is below 9.5

If any device runs an affected OS version listed above, it is vulnerable to this buffer overflow flaw in image processing.

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 9.5 / 11.7.7 / 12.6.6 or later
Fixed in 9.511.7.712.6.6
Interim mitigation

Update all affected devices to the patched versions: iOS 15.7.6/16.5+, iPadOS 15.7.6/16.5+, macOS Ventura 13.4+, macOS Big Sur 11.7.7+, macOS Monterey 12.6.6+, tvOS 16.5+, and watchOS 9.5+.

Recommended fix High confidence

iOS 15.7.6 / iOS 16.5, iPadOS 15.7.6 / 16.5, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4, watchOS 9.5, tvOS 16.5

  1. Verify current device OS version in Settings > General > About (iOS/iPadOS) or System Preferences > General > About (macOS)
  2. For iPhone/iPad: Back up important data via iCloud or computer
  3. Connect device to power and ensure stable internet connection
  4. Install the latest available security update: For iOS 15.x devices, upgrade to iOS 15.7.6; For iOS 16.x devices, upgrade to iOS 16.5 and iPadOS 16.5; For macOS Big Sur (11.x), upgrade to 11.7.7; For macOS Monterey (12.x), upgrade to 12.6.6; For macOS Ventura (13.x), upgrade to 13.4; For Apple Watch, upgrade to watchOS 9.5; For Apple TV, upgrade to tvOS 16.5
  5. On iOS/iPadOS go to Settings > General > Software Update and download/install the update
  6. On macOS go to System Preferences > Software Update or System Settings > General > Software Update
  7. Restart device after update completes
  8. Verify the update was applied by checking Settings > General > About again
Caveat Standard OS update considerations apply - ensure app compatibility and backup data before upgrading

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

Fix this in Ipados 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-2023-32384 — 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-2023-32384 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