dbcve.org
IpadosOperating system · Apple

CVE-2023-28200

MEDIUM · 5.5 CVSS v3.1 Published 2023-05-08
Fix available
A fix is available. Upgrade to 11.7.5 / 12.6.4 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
A validation issue was addressed with improved input sanitization. This issue is fixed in macOS Ventura 13.3, iOS 15.7.4 and iPadOS 15.7.4, macOS Monterey 12.6.4, macOS Big Sur 11.7.5. An app may be able to disclose kernel 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

A validation/input sanitization flaw in the macOS and iOS kernel allows a local application to read kernel memory due to improper input handling. This is a memory disclosure vulnerability where an app can potentially access sensitive kernel memory contents.

MitigationApply Apple's security updates: macOS Ventura 13.3, iOS/iPadOS 15.7.4, macOS Monterey 12.6.4, or macOS Big Sur 11.7.5 depending on the affected system. This is an OS-level patch that requires standard system updates.

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
Iphone OsOperating system
Affected:< 15.7.4
macOSOperating system
Affected:>= 11.0, < 11.7.5>= 12.0, < 12.6.4>= 13.0, < 13.3= 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. Identify the operating system
    Determine if the system is running macOS, iOS, or iPadOS. On macOS, open Terminal and run 'sw_vers' or check System Settings > About. On iOS/iPadOS, go to Settings > General > About.
    Affected if Any Apple device running macOS or iOS/iPadOS
  2. Check macOS version
    Run 'sw_vers' in Terminal or check System Settings > General > About This Mac. Note the exact version number (e.g., 13.2.1, 12.5, 11.7.4).
    Affected if The system is running macOS and the version falls within: 11.0 to 11.7.4 inclusive, 12.0 to 12.6.3 inclusive, 13.0 to 13.2.x inclusive, or exactly 13.4
  3. Check iOS/iPadOS version
    Go to Settings > General > About on the device and note the version number (e.g., 15.7.3, 16.0).
    Affected if The system is running iOS or iPadOS and the version is below 15.7.4 (versions 15.x below 15.7.4 are affected)
  4. Verify patch status
    Check if the system has received the latest Apple security updates. On macOS, go to System Settings > General > Software Update. On iOS/iPadOS, go to Settings > General > Software Update.
    Affected if The installed version has not been updated to the patched versions: macOS 11.7.5, 12.6.4, 13.3, or iOS/iPadOS 15.7.4

The system is affected if it runs any unpatched macOS version from 11.0 through 11.7.4, 12.0 through 12.6.3, 13.0 through 13.2.x, or exactly 13.4, or any iOS/iPadOS version below 15.7.4.

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 Apple's security updates: macOS Ventura 13.3, iOS/iPadOS 15.7.4, macOS Monterey 12.6.4, or macOS Big Sur 11.7.5 depending on the affected system. This is an OS-level patch that requires standard system updates.

Recommended fix High confidence

iOS 15.7.4+, iPadOS 15.7.4+, macOS Big Sur 11.7.5+, macOS Monterey 12.6.4+, macOS Ventura 13.3+

  1. Back up your device using iCloud or Finder/iTunes before performing any system update
  2. On iOS/iPadOS: Go to Settings > General > Software Update and install the available update to version 15.7.4 or later
  3. On macOS: Open System Preferences (or System Settings on Ventura) > Software Update and install the available security update for your version
  4. Alternatively, download and install the appropriate IPSW (iOS) or PKG (macOS) from Apple's official downloads page
  5. After updating, verify the installed version by checking Settings > General > About (iOS/iPadOS) or System Settings > General > About (macOS)
Caveat Standard risk associated with any OS update; ensure backups exist; some legacy apps may be incompatible with newer OS versions

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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