dbcve.org
IpadosOperating system · Apple

CVE-2023-28185

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to 9.4 / 11.7.5 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 integer overflow was addressed through improved input validation. This issue is fixed in tvOS 16.4, macOS Big Sur 11.7.5, iOS 16.4 and iPadOS 16.4, watchOS 9.4, macOS Monterey 12.6.4, iOS 15.7.4 and iPadOS 15.7.4. An app may be able to cause a denial-of-service.

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 · moderate confidence

Integer overflow vulnerability in Apple's iOS, iPadOS, macOS, watchOS, and tvOS allows a malicious app to cause a denial-of-service. The issue was fixed through improved input validation in the specified versions.

MitigationUpdate affected Apple devices to the patched versions: iOS 16.4/15.7.4, iPadOS 16.4/15.7.4, macOS Big Sur 11.7.5, macOS Monterey 12.6.4, watchOS 9.4, or tvOS 16.4.

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.0, < 15.7.4>= 16.0, < 16.4
Iphone OsOperating system
Affected:>= 15.0, < 15.7.4>= 16.0, < 16.4
macOSOperating system
Affected:>= 11.0, < 11.7.5>= 12.0.0, < 12.6.4
TvosOperating system
Affected:< 16.4
WatchosOperating system
Affected:< 9.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 iOS or iPadOS version
    Go to Settings > General > About > Version on the device
    Affected if Version is 15.0 to 15.7.3, or 16.0 to 16.3
  2. Check macOS version
    Go to Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if Version is 11.0 to 11.7.4, or 12.0.0 to 12.6.3
  3. Check watchOS version
    Open the Watch app on paired iPhone, go to My Watch > General > About, or check Settings > General > About on the watch
    Affected if Version is any version below 9.4
  4. Check tvOS version
    Go to Settings > General > About > Version on Apple TV
    Affected if Version is any version below 16.4

You are affected if your device runs any iOS 15.0-15.7.3, iOS 16.0-16.3, iPadOS 15.0-15.7.3, iPadOS 16.0-16.3, macOS 11.0-11.7.4, macOS 12.0.0-12.6.3, watchOS below 9.4, or tvOS below 16.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 9.4 / 11.7.5 / 12.6.4 or later
Fixed in 9.411.7.512.6.4
Interim mitigation

Update affected Apple devices to the patched versions: iOS 16.4/15.7.4, iPadOS 16.4/15.7.4, macOS Big Sur 11.7.5, macOS Monterey 12.6.4, watchOS 9.4, or tvOS 16.4.

Recommended fix High confidence

iOS 15.7.4 or iOS 16.4; iPadOS 15.7.4 or iPadOS 16.4; macOS Big Sur 11.7.5 or macOS Monterey 12.6.4; tvOS 16.4; watchOS 9.4

  1. Check current device OS version in Settings > General > About (iOS/iPadOS/watchOS) or System Preferences > General > About (macOS)
  2. Back up your device data before proceeding with the update
  3. For iOS/iPadOS: Go to Settings > General > Software Update and download/install the available update
  4. For macOS: Go to System Preferences > Software Update and download/install the available update
  5. For tvOS: Go to Settings > General > Apple TV Software Update and update to tvOS 16.4
  6. For watchOS: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 9.4
  7. After updating, verify the new OS version matches the fixed release (15.7.4, 16.4, 11.7.5, 12.6.4, or 9.4 as applicable)
Caveat Routine security updates with no expected breaking changes; standard iOS/macOS update precautions apply (backup recommended)

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

Fix this in Ipados Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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