dbcve.org
macOSOperating system · Apple

CVE-2023-32383

HIGH · 7.8 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to 11.7.7 / 12.6.6 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
This issue was addressed by forcing hardened runtime on the affected binaries at the system level. This issue is fixed in macOS Monterey 12.6.6, macOS Big Sur 11.7.7, macOS Ventura 13.4. An app may be able to inject code into sensitive binaries bundled with Xcode.

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 local application could inject code into sensitive Xcode binaries due to missing hardened runtime enforcement. This allowed a malicious app to potentially execute arbitrary code within Xcode's process space by targeting bundled development tools.

MitigationApply the macOS security updates (Monterey 12.6.6, Big Sur 11.7.7, or Ventura 13.4) which enforce hardened runtime at the system level, or upgrade to later supported macOS versions.

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.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
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 your macOS version
    Run 'sw_vers -productVersion' in Terminal or open System Settings > About This Mac
    Affected if The version is < 11.7.7, or between 12.0.0 and 12.6.5, or between 13.0 and 13.3.x
  2. Confirm Xcode is installed
    Run 'xcode-select -p' or verify /Applications/Xcode.app exists
    Affected if Xcode development tools are present on an affected macOS version
  3. Identify exact macOS build number (optional)
    Run 'system_profiler SPSoftwareDataType' or 'uname -a' to see full system details
    Affected if Build number corresponds to an affected macOS release (for precise confirmation)

You are affected if Xcode is installed on a macOS version that falls within the vulnerable ranges: < 11.7.7, 12.0.0-12.6.5, or 13.0-13.3.x

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 macOS security updates (Monterey 12.6.6, Big Sur 11.7.7, or Ventura 13.4) which enforce hardened runtime at the system level, or upgrade to later supported macOS versions.

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. Back up your Mac using Time Machine or another backup solution before proceeding with the system upgrade.
  2. Open System Preferences (or System Settings on macOS Ventura and later).
  3. Click on Software Update to check for available updates.
  4. The system will detect the appropriate update based on your current macOS version: For macOS Big Sur users, upgrade to version 11.7.7 or later; For macOS Monterey users, upgrade to version 12.6.6 or later; For macOS Ventura users, upgrade to version 13.4 or later.
  5. Click Download and Install to begin the update process.
  6. Follow the on-screen instructions and restart your Mac when prompted to complete the installation.
  7. After restarting, verify the update by going to Apple menu > About This Mac to confirm the installed macOS version matches the target fixed version.
Caveat Standard macOS upgrade considerations apply - review app compatibility and ensure backups are current before proceeding

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

Fix this in macOS Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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