IpadosOperating system · Apple

CVE-2023-41070

MEDIUM · 5.5 CVSS v3.1 Published 2023-09-27
Fix available
A fix is available. Upgrade to 10.0 / 13.6 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 logic issue was addressed with improved checks. This issue is fixed in macOS Ventura 13.6, iOS 16.7 and iPadOS 16.7, watchOS 10, iOS 17 and iPadOS 17, macOS Sonoma 14. An app may be able to access sensitive data logged when a user shares a link.

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 logic flaw in Apple's share functionality where an app can access sensitive data that gets logged when a user shares a link. The vulnerability stems from insufficient access controls on the logged data, allowing unauthorized apps to read information that should be protected during the link sharing process.

MitigationUpdate affected Apple devices to the fixed versions: macOS Ventura 13.6+, macOS Sonoma 14+, iOS/iPadOS 16.7+, iOS/iPadOS 17+, or watchOS 10+.

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
Iphone OsOperating system
Affected:< 16.7
macOSOperating system
Affected:>= 13.0, < 13.6
WatchosOperating system
Affected:< 10.0

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 or iPadOS version
    Go to Settings > General > About on iPhone or iPad, or check the model and iOS version via iTunes/Finder when connected to a computer
    Affected if The installed iOS version is below 16.7 or iPadOS version is below 16.7
  2. Check macOS version
    Click the Apple menu > About This Mac to view the macOS version number
    Affected if The installed macOS version is 13.0 through 13.5 (Ventura 13.6+ is fixed)
  3. Check watchOS version
    Open the Watch app on iPhone, select your watch, then go to General > About to view watchOS version
    Affected if The installed watchOS version is below 10.0
  4. Understand the vulnerability context
    This is a logic flaw in the built-in share sheet - no user-configurable setting exists to verify. The flaw allows any app with certain permissions to access sensitive data that gets logged during link sharing.
    Affected if Your device runs a vulnerable OS version and you use the share functionality to share links with third-party apps

You are affected if your device runs iOS/iPadOS below 16.7, macOS 13.0-13.5, or watchOS below 10.0, and you use the share sheet to share links with applications.

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.0 / 13.6 / 16.7 or later
Fixed in 10.013.616.7
Interim mitigation

Update affected Apple devices to the fixed versions: macOS Ventura 13.6+, macOS Sonoma 14+, iOS/iPadOS 16.7+, iOS/iPadOS 17+, or watchOS 10+.

Recommended fix High confidence

iOS 16.7, iPadOS 16.7, macOS 13.6 Ventura, watchOS 10 (or newer releases)

  1. For iPhone: Navigate to Settings > General > Software Update and install iOS 16.7 or later
  2. For iPad: Navigate to Settings > General > Software Update and install iPadOS 16.7 or later
  3. For Mac: Open System Settings > General > Software Update and install macOS 13.6 Ventura or later
  4. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and install watchOS 10 or later
  5. After updating, verify the update was successful by checking the OS version in Settings/About
Caveat iOS 17/iPadOS 17/macOS Sonoma have newer hardware requirements; ensure device compatibility before upgrading to those versions

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41070 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-41070 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