dbcve.org
macOSOperating system · Apple

CVE-2023-32387

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A use-after-free issue was addressed with improved memory management. This issue is fixed in macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4. A remote attacker may be able to cause unexpected app termination or 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 use-after-free vulnerability in macOS allows a remote attacker to execute arbitrary code or cause application termination. The issue stems from improper memory management where memory is accessed after being freed.

MitigationApply the available macOS security updates (Big Sur 11.7.7, Monterey 12.6.6, or Ventura 13.4) to all affected systems as soon as possible to remediate the vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 or go to System Settings > About to view the macOS version
    Affected if The version displayed is within the affected ranges: 11.0.0 to 11.7.6, 12.0.0 to 12.6.5, or 13.0 to 13.3
  2. Confirm macOS build date
    Run 'sw_vers' in Terminal to see the build version (e.g., 22G90 for Ventura 13.3)
    Affected if The build version corresponds to an unpatched release prior to the fixed builds (11.7.7, 12.6.6, or 13.4)
  3. Verify system is not up-to-date
    Check System Settings > General > Software Update for available updates
    Affected if Security updates for this CVE are not installed and the system shows an available update to version 11.7.7, 12.6.6, or 13.4 or later

A system is affected if it runs any unpatched version of macOS Big Sur 11.0.0-11.7.6, Monterey 12.0.0-12.6.5, or Ventura 13.0-13.3.

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 as soon as possible to remediate the vulnerability.

Recommended fix High confidence

macOS Big Sur 11.7.7, macOS Monterey 12.6.6, or macOS Ventura 13.4 (depending on which major version line you are on)

  1. 1. Back up important data on the macOS device before starting the upgrade process.
  2. 2. Connect the Mac to a reliable power source and stable internet connection.
  3. 3. Open System Settings (System Preferences on older macOS versions).
  4. 4. Navigate to General > Software Update (or click the Apple menu > About This Mac > Software Update).
  5. 5. Allow the system to check for available updates.
  6. 6. Select and install the appropriate update: macOS Ventura 13.4 or later, macOS Monterey 12.6.6, or macOS Big Sur 11.7.7, depending on your current macOS version.
  7. 7. Follow the on-screen instructions to complete the installation.
  8. 8. Restart the Mac when prompted to apply the security update.
Caveat Security updates may include compatibility changes; verify critical applications are supported on the target macOS version before upgrading

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

Fix this in macOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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