dbcve.org
macOSOperating system · Apple

CVE-2023-32380

HIGH · 7.8 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 11.7.7 / 12.6.6 or later.
See remediation →
80/100
Remediation priority · High
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
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4. Processing a 3D model 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

An out-of-bounds write vulnerability exists in macOS 3D model processing functionality. Insufficient bounds checking during parsing of 3D model files allows memory corruption that can be leveraged for arbitrary code execution. The vulnerability is triggered when a user processes a maliciously crafted 3D model file.

MitigationApply the available macOS security updates (Big Sur 11.7.7, Monterey 12.6.6, or Ventura 13.4) to all affected systems. Avoid opening untrusted 3D model files from unknown 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
macOSOperating system
Affected:>= 11.0, < 11.7.7>= 12.0.0, < 12.6.6>= 13.0, < 13.4

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 installed macOS version
    Run 'sw_vers -ProductVersion' in Terminal to obtain the current macOS version number
    Affected if The version is 11.0 to 11.7.6, 12.0.0 to 12.6.5, or 13.0 to 13.3.x (any version below 11.7.7, 12.6.6, or 13.4)
  2. Confirm 3D model processing capability present
    Verify that Model I/O framework exists by checking '/System/Library/Frameworks/ModelIO.framework' exists - this framework handles 3D model file parsing in macOS
    Affected if The Model I/O framework is present on the system (default in all affected macOS versions)
  3. Identify 3D model file types supported
    Check for presence of 3D model file support by running 'mdimport -r' and inspecting common 3D formats: .obj, .dae, .scn, .usdz, .ply in typical locations like ~/Downloads or ~/Documents
    Affected if The system supports processing of 3D model files (built-in functionality in affected macOS versions)
  4. Review recent Quick Look or Preview activity for 3D files
    Run 'sqlite3 ~/Library/Application Support/Quick Look/recent.db "SELECT * FROM recent_items WHERE content_type LIKE '%3d%' OR content_type LIKE '%model%' LIMIT 20;"' to check if any 3D model files were recently viewed via Quick Look
    Affected if Any 3D model files (.obj, .dae, .scn, .usdz, .ply) were opened on the system after the affected OS version was installed

The system is potentially affected if the macOS version falls within 11.0 to 11.7.6, 12.0.0 to 12.6.5, or 13.0 to 13.3.x AND the system has processed any 3D model files using built-in macOS frameworks.

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

Apply the available macOS security updates (Big Sur 11.7.7, Monterey 12.6.6, or Ventura 13.4) to all affected systems. Avoid opening untrusted 3D model files from unknown sources until patches are applied.

Recommended fix High confidence

macOS Big Sur 11.7.7 (for systems on 11.x), macOS Monterey 12.6.6 (for systems on 12.x), or macOS Ventura 13.4 (for systems on 13.x)

  1. Back up all important data on the affected Mac before proceeding with the update
  2. Go to Apple menu > System Settings (or System Preferences on older macOS versions)
  3. Click on General > Software Update
  4. Allow macOS to check for available updates
  5. If an update is available, click Download and Install
  6. Wait for the download to complete, then follow the on-screen instructions to install the update
  7. Restart your Mac when prompted to complete the installation
Caveat Upgrading to a newer macOS version may introduce compatibility issues with older applications or require reconfiguration of system settings

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

Fix this in macOS Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,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 $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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