dbcve.org
IpadosOperating system · Apple

CVE-2023-42937

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 10.2 / 12.7.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 iOS 16.7.5 and iPadOS 16.7.5, watchOS 10.2, macOS Ventura 13.6.4, macOS Sonoma 14.2, macOS Monterey 12.7.3, iOS 17.2 and iPadOS 17.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

A privacy vulnerability in Apple operating systems allowed applications to access sensitive user data through insufficiently redacted log entries. The issue stemmed from improper handling of private data in system logs, potentially exposing confidential user information to malicious or compromised applications.

MitigationApply the appropriate security updates for affected platforms: iOS 16.7.5/17.2, iPadOS 16.7.5/17.2, watchOS 10.2, macOS Ventura 13.6.4, macOS Sonoma 14.2, or macOS Monterey 12.7.3.

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.0, < 16.7.5> 17.0, < 17.2
Iphone OsOperating system
Affected:> 16.0, < 16.7.5> 17.0, < 17.2
macOSOperating system
Affected:>= 12.0, < 12.7.3>= 13.0, < 13.6.4>= 14.0, < 14.2
WatchosOperating system
Affected:< 10.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 iOS version
    Go to Settings > General > About on the iPhone and locate the 'Version' field
    Affected if The version shows iOS 16.0 through 16.7.4, or iOS 17.0 through 17.1
  2. Check iPadOS version
    Go to Settings > General > About on the iPad and locate the 'Version' field
    Affected if The version shows iPadOS 16.0 through 16.7.4, or iPadOS 17.0 through 17.1
  3. Check macOS version
    Click the Apple menu > About This Mac and note the version number under macOS
    Affected if The version shows 12.0 through 12.7.2, 13.0 through 13.6.3, or 14.0 through 14.1
  4. Check watchOS version
    Open the Watch app on iPhone, select your watch, go to General > About, and note the watchOS version
    Affected if The version shows any version below 10.2

You are affected if any Apple device (iPhone, iPad, Mac, or Apple Watch) runs an OS version within the affected ranges listed above.

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.2 / 12.7.3 / 13.6.4 or later
Fixed in 10.212.7.313.6.4
Interim mitigation

Apply the appropriate security updates for affected platforms: iOS 16.7.5/17.2, iPadOS 16.7.5/17.2, watchOS 10.2, macOS Ventura 13.6.4, macOS Sonoma 14.2, or macOS Monterey 12.7.3.

Recommended fix High confidence

iOS 16.7.5 / iOS 17.2, iPadOS 16.7.5 / iPadOS 17.2, macOS 12.7.3 / 13.6.4 / 14.2, watchOS 10.2 (depending on current major version)

  1. Identify the current installed OS version on the device (iOS, iPadOS, macOS, or watchOS)
  2. For iOS devices: If running iOS 16.x (between 16.0 and 16.7.4), upgrade to iOS 16.7.5. If running iOS 17.x (between 17.0 and 17.1), upgrade to iOS 17.2
  3. For iPadOS devices: If running iPadOS 16.x (between 16.0 and 16.7.4), upgrade to iPadOS 16.7.5. If running iPadOS 17.x (between 17.0 and 17.1), upgrade to iPadOS 17.2
  4. For macOS Monterey (12.x): Upgrade to macOS Monterey 12.7.3
  5. For macOS Ventura (13.x): Upgrade to macOS Ventura 13.6.4
  6. For macOS Sonoma (14.x): Upgrade to macOS Sonoma 14.2
  7. For Apple Watch: Upgrade to watchOS 10.2
  8. Perform the upgrade via Settings > General > Software Update on iOS/iPadOS/WatchOS, or System Preferences > Software Update on macOS
Caveat Standard OS update risks apply (ensure backups exist before updating)

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-42937 — 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-42937 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