dbcve.org
IpadosOperating system · Apple

CVE-2024-23231

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-08
Fix available
A fix is available. Upgrade to 10.4 / 13.6.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
A privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in iOS 16.7.6 and iPadOS 16.7.6, iOS 17.4 and iPadOS 17.4, macOS Sonoma 14.4, macOS Ventura 13.6.5, watchOS 10.4. An app may be able to access user-sensitive data.

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

A privacy vulnerability in Apple's logging subsystem allowed applications to potentially access sensitive user data due to insufficient redaction of private information in system log entries. The fix involved improved private data redaction for log entries across iOS, iPadOS, macOS, and watchOS.

MitigationApply the appropriate Apple security updates for your platform: iOS 16.7.6 or later, iOS 17.4 or later, iPadOS 16.7.6 or later, iPadOS 17.4 or later, macOS Ventura 13.6.5 or later, macOS Sonoma 14.4 or later, or watchOS 10.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:< 16.7.6>= 17.0, < 17.4
Iphone OsOperating system
Affected:< 16.7.6>= 17.0, < 17.4
macOSOperating system
Affected:>= 13.0, < 13.6.5>= 14.0, < 14.4
WatchosOperating system
Affected:< 10.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 > Version, or use the 'About This Mac' app if checking an iPhone connected to a Mac
    Affected if Version is below 16.7.6, or between 17.0 and 17.3 (inclusive)
  2. Check iPadOS version on iPad
    Go to Settings > General > About > Version, or use the 'About This Mac' app if checking an iPad connected to a Mac
    Affected if Version is below 16.7.6, or between 17.0 and 17.3 (inclusive)
  3. Check macOS version on Mac
    Run 'sw_vers' in Terminal, or go to System Settings > About
    Affected if Version is 13.0 to 13.6.4, or 14.0 to 14.3 (inclusive)
  4. Check watchOS version on Apple Watch
    Open the Watch app on paired iPhone, go to General > About, or open Settings on Apple Watch and go to General > About
    Affected if Version is below 10.4

If your device runs any of the affected OS versions listed above, the logging subsystem may not properly redact private user data in system log entries.

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 10.4 / 13.6.5 / 14.4 or later
Fixed in 10.413.6.514.4
Interim mitigation

Apply the appropriate Apple security updates for your platform: iOS 16.7.6 or later, iOS 17.4 or later, iPadOS 16.7.6 or later, iPadOS 17.4 or later, macOS Ventura 13.6.5 or later, macOS Sonoma 14.4 or later, or watchOS 10.4 or later.

Recommended fix High confidence

iOS 16.7.6 / iPadOS 16.7.6 / iOS 17.4 / iPadOS 17.4 / macOS Ventura 13.6.5 / macOS Sonoma 14.4 / watchOS 10.4 (depending on current device and OS version)

  1. Identify the Apple device type (iPhone, iPad, Mac, or Apple Watch)
  2. Determine the current installed OS version from Settings > General > About
  3. For iPhone/iPad: If running iOS/iPadOS 16.x, upgrade to 16.7.6; if running iOS/iPadOS 17.x, upgrade to 17.4
  4. For Mac: If running macOS Ventura (13.x), upgrade to 13.6.5; if running macOS Sonoma (14.x), upgrade to 14.4
  5. For Apple Watch: Upgrade to watchOS 10.4
  6. Install the update via Settings > General > Software Update (iOS/iPadOS/watchOS) or System Settings > Software Update (macOS)
  7. Restart the device after installation to complete the update

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-2024-23231 — 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-2024-23231 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