dbcve.org
Ipad OsOperating system · Apple

CVE-2023-42946

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 10.1 / 17.1 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
This issue was addressed with improved redaction of sensitive information. This issue is fixed in tvOS 17.1, watchOS 10.1, macOS Sonoma 14.1, iOS 17.1 and iPadOS 17.1. An app may be able to leak sensitive user information.

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

This is a privacy vulnerability in Apple operating systems where improper redaction of sensitive information allowed an application to potentially leak user data. The vulnerability was addressed through improved redaction mechanisms in the affected OS versions.

MitigationApply the vendor-supplied updates: iOS 17.1, iPadOS 17.1, watchOS 10.1, tvOS 17.1, or macOS Sonoma 14.1 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
Ipad OsOperating system
Affected:< 17.1
Iphone OsOperating system
Affected:< 17.1
macOSOperating system
Affected:= 14.0
TvosOperating system
Affected:< 17.1
WatchosOperating system
Affected:< 10.1

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 Apple device and platform
    Determine whether the device is an iPhone, iPad, Mac, Apple TV, or Apple Watch. Each platform has a different way to check the OS version.
    Affected if Any Apple device running an affected OS version as listed below.
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and look at the 'Version' field. The format will be like 17.0.x or 16.x.x.
    Affected if Version is less than 17.1 (for example, 17.0, 16.x, 15.x). Versions 17.1 and later are patched.
  3. Check macOS version
    On Mac, go to System Settings > About (or Apple menu > About This Mac) and look at the 'macOS' or 'Version' field. It will display something like 14.0, 14.1, etc.
    Affected if Version is exactly 14.0 (the specific affected version). Versions 14.1 and later are patched.
  4. Check tvOS version
    On Apple TV, go to Settings > General > About and look at the 'Version' field.
    Affected if Version is less than 17.1 (for example, 17.0, 16.x). Versions 17.1 and later are patched.
  5. Check watchOS version
    On the iPhone paired with the Apple Watch, open the Watch app, go to General > About, and check the 'Watch Version' field. Alternatively, check directly on Apple Watch via Settings > General > About.
    Affected if Version is less than 10.1 (for example, 10.0, 9.x). Versions 10.1 and later are patched.

A user is affected if their device runs iOS/iPadOS/tvOS/watchOS version below 17.1 (or 10.1 for watchOS), or if their Mac runs exactly macOS 14.0.

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.1 / 17.1 or later
Fixed in 10.117.1
Interim mitigation

Apply the vendor-supplied updates: iOS 17.1, iPadOS 17.1, watchOS 10.1, tvOS 17.1, or macOS Sonoma 14.1 or later.

Recommended fix High confidence

iOS 17.1, iPadOS 17.1, macOS Sonoma 14.1, tvOS 17.1, watchOS 10.1

  1. For iPhone and iPad: Go to Settings > General > Software Update and update to iOS 17.1 or iPadOS 17.1
  2. For Mac: Go to System Settings > General > Software Update and update to macOS Sonoma 14.1
  3. For Apple TV: Go to Settings > System > Software Updates and update to tvOS 17.1
  4. For Apple Watch: Go to Settings > General > Software Update on the paired iPhone, or directly on the watch, and update to watchOS 10.1

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

Fix this in Ipad Os 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-42946 — 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-42946 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