dbcve.org
IpadosOperating system · Apple

CVE-2023-42919

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 12.7.2 / 13.6.3 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 macOS Sonoma 14.2, iOS 17.2 and iPadOS 17.2, watchOS 10.2, macOS Ventura 13.6.3, iOS 16.7.3 and iPadOS 16.7.3, macOS Monterey 12.7.2. An app may be able to access sensitive user 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 · high confidence

This vulnerability involves improper private data redaction in system log entries across multiple Apple operating systems. An application could potentially access sensitive user data that should have been redacted from logs. The issue was addressed by implementing improved redaction mechanisms in the affected OS versions.

MitigationUpdate all affected devices to macOS Sonoma 14.2, iOS/iPadOS 17.2, watchOS 10.2, macOS Ventura 13.6.3, iOS/iPadOS 16.7.3, or macOS Monterey 12.7.2 or later to incorporate the fixed log redaction logic.

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.3>= 17.0, < 17.2
Iphone OsOperating system
Affected:< 16.7.3>= 17.0, < 17.2
macOSOperating system
Affected:>= 12.0.0, < 12.7.2>= 13.0, < 13.6.3>= 14.0, < 14.2

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 macOS version
    Open Terminal and run: sw_vers -productVersion
    Affected if version is 12.0.0 to 12.7.1, 13.0 to 13.6.2, or 14.0 to 14.1.x
  2. Check iOS or iPadOS version
    Open Settings > General > About on the device and note the version number
    Affected if version is 16.7.2 or earlier, or 17.0 to 17.1.x
  3. Identify all affected Apple devices on your network
    Use your device management console or manually check each device: macOS via System Preferences > About, iOS/iPadOS via Settings > General > About
    Affected if any device runs a vulnerable OS version listed in step 1 or 2

You are affected if any Apple device (Mac, iPhone, or iPad) in your environment runs a version of macOS before 12.7.2, 13.x before 13.6.3, or 14.x before 14.2; or iOS/iPadOS before 16.7.3 or 17.x before 17.2.

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 12.7.2 / 13.6.3 / 14.2 or later
Fixed in 12.7.213.6.314.2
Interim mitigation

Update all affected devices to macOS Sonoma 14.2, iOS/iPadOS 17.2, watchOS 10.2, macOS Ventura 13.6.3, iOS/iPadOS 16.7.3, or macOS Monterey 12.7.2 or later to incorporate the fixed log redaction logic.

Recommended fix High confidence

iOS 16.7.3+ or iOS 17.2+ | iPadOS 16.7.3+ or iPadOS 17.2+ | macOS 12.7.2+ (Monterey), 13.6.3+ (Ventura), or 14.2+ (Sonoma)

  1. Identify the current iOS/iPadOS/macOS version on the device by going to Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
  2. For iOS/iPadOS: Go to Settings > General > Software Update to check for and install available updates
  3. For macOS: Go to System Settings > Software Update to check for and install available updates
  4. Ensure the device is connected to Wi-Fi and has sufficient battery (or is charging) before updating
  5. After updating, verify the device is running iOS 16.7.3 or later (for iPhone), iPadOS 16.7.3 or later (for iPad), or macOS 12.7.2/13.6.3/14.2 or later depending on the original OS version
Caveat Major OS version upgrades (e.g., from macOS 12 to 14) may introduce app compatibility changes; review app compatibility before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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