dbcve.org
IpadosOperating system · Apple

CVE-2023-27963

HIGH · 7.5 CVSS v3.1 Published 2023-05-08
Fix available
A fix is available. Upgrade to 9.4 / 12.6.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The issue was addressed with additional permissions checks. This issue is fixed in macOS Ventura 13.3, iOS 16.4 and iPadOS 16.4, iOS 15.7.4 and iPadOS 15.7.4, macOS Monterey 12.6.4, tvOS 16.4, watchOS 9.4. A shortcut may be able to use sensitive data with certain actions without prompting the user.

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 vulnerability in Apple's Shortcuts application allowed shortcuts to access sensitive data without proper user prompting due to insufficient permissions checks. The issue was addressed by implementing additional permission validation gates before allowing shortcuts to use sensitive data with certain actions.

MitigationUpdate affected devices to the fixed OS versions: macOS Ventura 13.3+, macOS Monterey 12.6.4+, iOS/iPadOS 16.4+, iOS/iPadOS 15.7.4+, tvOS 16.4+, or watchOS 9.4+.

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:< 15.7.4>= 16.0, < 16.4
Iphone OsOperating system
Affected:< 15.7.4>= 16.0, < 16.4
macOSOperating system
Affected:>= 12.0, < 12.6.4>= 13.0, < 13.3
WatchosOperating system
Affected:< 9.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 your device's iOS or iPadOS version
    Go to Settings > General > About and note the version number shown next to 'Version'
    Affected if The version is less than 15.7.4, or is 16.0 through 16.3 (any version >= 16.0 but < 16.4)
  2. Check your Mac's macOS version
    Click the Apple menu > About This Mac and note the version under 'macOS'
    Affected if The version is 12.0 through 12.6.3 (any version >= 12.0 but < 12.6.4), or 13.0 through 13.2 (any version >= 13.0 but < 13.3)
  3. Check your Apple Watch's watchOS version
    Open the Watch app on your iPhone, go to My Watch > General > About and note the version
    Affected if The version is any version below 9.4

You are affected if your device runs any iOS/iPadOS version < 15.7.4 or >= 16.0 but < 16.4, any macOS version >= 12.0 but < 12.6.4 or >= 13.0 but < 13.3, or any watchOS version < 9.4.

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 9.4 / 12.6.4 / 13.3 or later
Fixed in 9.412.6.413.3
Interim mitigation

Update affected devices to the fixed OS versions: macOS Ventura 13.3+, macOS Monterey 12.6.4+, iOS/iPadOS 16.4+, iOS/iPadOS 15.7.4+, tvOS 16.4+, or watchOS 9.4+.

Recommended fix High confidence

iOS 15.7.4 / iOS 16.4, iPadOS 15.7.4 / iPadOS 16.4, macOS Monterey 12.6.4, macOS Ventura 13.3, watchOS 9.4

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 15.7.4 or later (or iOS/iPadOS 16.4 or later for newer devices)
  2. For Mac: Go to System Settings > General > Software Update and install macOS Monterey 12.6.4 or later (or macOS Ventura 13.3 or later)
  3. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update, and install watchOS 9.4 or later

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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