macOSOperating system · Apple

CVE-2023-32382

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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 read was addressed with improved input validation. 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 result in disclosure of process memory.

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

This is an out-of-bounds read vulnerability in macOS that occurs when processing 3D models. The flaw allows an attacker to read process memory beyond allocated boundaries due to insufficient input validation on 3D model data. This can lead to disclosure of sensitive process memory contents.

MitigationUpdate macOS to version Big Sur 11.7.7, Monterey 12.6.6, Ventura 13.4 or later to patch the vulnerability. Avoid processing untrusted 3D model files until systems are patched.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 your macOS version
    Run 'sw_vers' in Terminal or go to Apple menu > About This Mac to view the macOS version number
    Affected if The version shown is 11.0 to 11.7.6, 12.0.0 to 12.6.5, or 13.0 to 13.3 (any version in the affected ranges)
  2. Verify the specific macOS release number
    Run 'sw_vers -productVersion' to get the exact version such as 11.7.5 or 13.3.1
    Affected if The version is less than 11.7.7, 12.6.6, or 13.4 respectively for your major release
  3. Identify if 3D model processing occurs
    Check if users on this system commonly open or preview 3D model files (.obj, .dae, .usdz, .stl, .fbx) using built-in macOS apps like Quick Look or Preview
    Affected if The system runs a vulnerable macOS version AND is used to open or preview untrusted 3D model files
  4. Review Quick Look preview handlers
    Run 'qlmanage -m' to list Quick Look plugins, which handle 3D model previews in Finder
    Affected if The system runs a vulnerable macOS version and Quick Look is enabled for 3D model file types

You are affected if your macOS version falls within 11.0 to 11.7.6, 12.0.0 to 12.6.5, or 13.0 to 13.3 and you or any user on the system processes 3D model files using built-in macOS features.

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

Update macOS to version Big Sur 11.7.7, Monterey 12.6.6, Ventura 13.4 or later to patch the vulnerability. Avoid processing untrusted 3D model files until systems are patched.

Recommended fix High confidence

macOS Big Sur 11.7.7, macOS Monterey 12.6.6, or macOS Ventura 13.4 (depending on your current major version)

  1. Open the Apple menu and select System Settings (or System Preferences on older macOS versions)
  2. Click on General, then select Software Update
  3. Allow macOS to check for available updates
  4. If the fixed version (11.7.7, 12.6.6, or 13.4) is shown, click Update Now to install it
  5. Restart your Mac if prompted to complete the installation

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

Fix this in macOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
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,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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