dbcve.org
IpadosOperating system · Apple

CVE-2023-32410

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 →
58/100
Remediation priority · Elevated
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 read was addressed with improved input validation. This issue is fixed in iOS 15.7.6 and iPadOS 15.7.6, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, macOS Ventura 13.4. An app may be able to leak sensitive kernel state.

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 kernel-level out-of-bounds read vulnerability in Apple iOS, iPadOS, and macOS allows a malicious application to read beyond allocated memory boundaries, potentially exposing sensitive kernel state information due to insufficient input validation.

MitigationApply the appropriate Apple security update: iOS 15.7.6/iPadOS 15.7.6 for mobile devices, or macOS Big Sur 11.7.7/macOS Monterey 12.6.6/macOS Ventura 13.4 for Macs.

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.6
Iphone OsOperating system
Affected:< 15.7.6
macOSOperating system
Affected:>= 11.0, < 11.7.7>= 12.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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 iOS version on iPhone
    Go to Settings > General > About and note the version number displayed next to 'Version'
    Affected if Version is less than 15.7.6 (e.g., 15.7.5 or earlier)
  2. Check iPadOS version on iPad
    Go to Settings > General > About and note the version number displayed next to 'Version'
    Affected if Version is less than 15.7.6 (e.g., 15.7.5 or earlier)
  3. Check macOS version on Mac
    Click the Apple menu > About This Mac and note the version number (e.g., 13.3, 12.5, 11.6)
    Affected if Version is 11.0 to 11.7.6, 12.0 to 12.6.5, or 13.0 to 13.3 (any version in the affected ranges)
  4. Confirm patch status
    On iOS/iPadOS: go to Settings > General > Software Update to see if 15.7.6 is installed. On macOS: go to System Settings > General > Software Update to verify the installed security update
    Affected if The specific security update (iOS 15.7.6, iPadOS 15.7.6, or the corresponding macOS update) is not installed

You are affected if your device runs any iOS/iPadOS version below 15.7.6, or any macOS version between 11.0 and 11.7.6, 12.0 and 12.6.5, or 13.0 and 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 appropriate Apple security update: iOS 15.7.6/iPadOS 15.7.6 for mobile devices, or macOS Big Sur 11.7.7/macOS Monterey 12.6.6/macOS Ventura 13.4 for Macs.

Recommended fix High confidence

iOS 15.7.6 / iPadOS 15.7.6 / macOS Big Sur 11.7.7 / macOS Monterey 12.6.6 / macOS Ventura 13.4

  1. For iPhone: Go to Settings > General > Software Update and install iOS 15.7.6
  2. For iPad: Go to Settings > General > Software Update and install iPadOS 15.7.6
  3. For macOS Big Sur (11.x): Go to System Preferences > Software Update and install macOS Big Sur 11.7.7
  4. For macOS Monterey (12.x): Go to System Preferences > Software Update and install macOS Monterey 12.6.6
  5. For macOS Ventura (13.x): Go to System Settings > Software Update and install macOS Ventura 13.4
  6. Alternatively, manually download the appropriate IPSW or installer from Apple's support website and restore the device
Caveat Standard Apple security update; minimal risk of breaking changes for typical users, but always backup data before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
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,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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