dbcve.org
IpadosOperating system · Apple

CVE-2023-32366

HIGH · 7.8 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to 11.7.5 / 12.6.4 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
An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in macOS Big Sur 11.7.5, macOS Ventura 13.3, iOS 16.4 and iPadOS 16.4, iOS 15.7.4 and iPadOS 15.7.4, macOS Monterey 12.6.4. Processing a font file 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

Out-of-bounds write vulnerability in font file processing within macOS and iOS allows arbitrary code execution when processing specially crafted malicious font files. The issue was addressed with improved input validation.

MitigationApply vendor security updates by upgrading to macOS Big Sur 11.7.5, macOS Monterey 12.6.4, macOS Ventura 13.3, iOS 15.7.4, iPadOS 15.7.4, iOS 16.4, or iPadOS 16.4 or later.

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.4>= 16.0, < 16.4
Iphone OsOperating system
Affected:< 15.7.4>= 16.0, < 16.4
macOSOperating system
Affected:< 11.7.5>= 12.0.0, < 12.6.4>= 13.0, < 13.3

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 macOS version on Mac computers
    Run 'sw_vers -ProductVersion' in Terminal or go to Apple menu > About This Mac
    Affected if The version is less than 11.7.5, OR between 12.0.0 and 12.6.4, OR between 13.0 and 13.3
  2. Check iOS version on iPhones
    Go to Settings > General > About on the device, or use Xcode or Apple Configurator to check the device
    Affected if The version is less than 15.7.4, OR between 16.0 and 16.4
  3. Check iPadOS version on iPads
    Go to Settings > General > About on the device, or use Xcode or Apple Configurator to check the device
    Affected if The version is less than 15.7.4, OR between 16.0 and 16.4
  4. Understand the attack vector
    The vulnerability is triggered when processing font files. Font file processing is a built-in system component (CoreText on Apple platforms). No specific feature needs to be enabled - any application or system service that processes fonts could be a trigger point.
    Affected if The OS version falls within any of the affected ranges listed above and untrusted font files can be opened or processed on the device

If the installed macOS, iOS, or iPadOS version falls within any of the affected ranges, the system is vulnerable when processing potentially malicious font files.

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.5 / 12.6.4 / 13.3 or later
Fixed in 11.7.512.6.413.3
Interim mitigation

Apply vendor security updates by upgrading to macOS Big Sur 11.7.5, macOS Monterey 12.6.4, macOS Ventura 13.3, iOS 15.7.4, iPadOS 15.7.4, iOS 16.4, or iPadOS 16.4 or later.

Recommended fix High confidence

iOS 15.7.4 or iOS 16.4; iPadOS 15.7.4 or iPadOS 16.4; macOS 11.7.5, 12.6.4, or 13.3 depending on current version

  1. For iOS devices: Update to iOS 15.7.4 (for iOS 15.x devices) or iOS 16.4 (for iOS 16.x devices) via Settings > General > Software Update
  2. For iPadOS devices: Update to iPadOS 15.7.4 (for iPadOS 15.x devices) or iPadOS 16.4 (for iPadOS 16.x devices) via Settings > General > Software Update
  3. For macOS Big Sur (11.x) devices: Update to macOS 11.7.5 via System Preferences > Software Update
  4. For macOS Monterey (12.x) devices: Update to macOS 12.6.4 via System Preferences > Software Update
  5. For macOS Ventura (13.x) devices: Update to macOS 13.3 via System Preferences > Software Update
Caveat Standard OS update considerations apply - backup data before updating, and ensure compatibility with dependent applications

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing2.0 h
  • Review / QA1.0 h
11.0 hours of engineering $1,960
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,136.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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