dbcve.org
IpadosOperating system · Apple

CVE-2023-40413

MEDIUM · 5.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 10.1 / 12.7.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
The issue was addressed with improved handling of caches. This issue is fixed in iOS 17.1 and iPadOS 17.1, macOS Monterey 12.7.1, watchOS 10.1, iOS 16.7.2 and iPadOS 16.7.2, macOS Ventura 13.6.1, macOS Sonoma 14.1. An app may be able to read sensitive location 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 · high confidence

A vulnerability in Apple's mobile and desktop operating systems allows a malicious or compromised application to read sensitive location information due to improper cache handling. The vulnerability is fixed in the listed iOS, iPadOS, macOS, and watchOS versions through improved cache management.

MitigationApply the vendor patches by updating affected devices to iOS 17.1/iPadOS 17.1, iOS 16.7.2/iPadOS 16.7.2, macOS Monterey 12.7.1, macOS Ventura 13.6.1, macOS Sonoma 14.1, or watchOS 10.1 as appropriate for each device.

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.2>= 17.0, < 17.1
Iphone OsOperating system
Affected:< 16.7.2>= 17.0, < 17.1
macOSOperating system
Affected:>= 12.0.0, < 12.7.1>= 13.0, < 13.6.1>= 14.0, < 14.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 type
    Determine whether the device is an iPhone, iPad, Mac, or Apple Watch. The affected OS versions differ by device category, so this first step is essential.
    Affected if The device runs iOS, iPadOS, macOS, or watchOS.
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the version number displayed next to 'Software Version'.
    Affected if The installed version is less than 16.7.2, or is 17.0 through 17.0.x (any 17.0.x version below 17.1).
  3. Check macOS version
    On Mac, click the Apple menu > About This Mac, or go to System Settings > About. Note the version number (such as 12.x, 13.x, or 14.x).
    Affected if The installed version is 12.0.0 through 12.7.0, 13.0 through 13.6.0, or 14.0 through 14.0.x.
  4. Check watchOS version
    On Apple Watch, go to Settings > General > About and note the watchOS version. Alternatively, open the Watch app on a paired iPhone, go to My Watch > General > About.
    Affected if The watchOS version is any version below 10.1 (including all 9.x versions).

The device is affected if it runs any iOS/iPadOS version below 16.7.2 or between 17.0 and 17.0.x, any macOS version between 12.0.0 and 12.7.0, 13.0 and 13.6.0, or 14.0 and 14.0.x, or any watchOS version below 10.1.

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 / 12.7.1 / 13.6.1 or later
Fixed in 10.112.7.113.6.1
Interim mitigation

Apply the vendor patches by updating affected devices to iOS 17.1/iPadOS 17.1, iOS 16.7.2/iPadOS 16.7.2, macOS Monterey 12.7.1, macOS Ventura 13.6.1, macOS Sonoma 14.1, or watchOS 10.1 as appropriate for each device.

Recommended fix High confidence

iOS 16.7.2/iOS 17.1, iPadOS 16.7.2/iPadOS 17.1, macOS Monterey 12.7.1, macOS Ventura 13.6.1, macOS Sonoma 14.1, or watchOS 10.1 (depending on device)

  1. For iPhone/iPad: Upgrade to iOS 16.7.2 or iPadOS 16.7.2 (or iOS 17.1/iPadOS 17.1 if moving to major version 17)
  2. For macOS Monterey (12.x): Upgrade to macOS Monterey 12.7.1
  3. For macOS Ventura (13.x): Upgrade to macOS Ventura 13.6.1
  4. For macOS Sonoma (14.x): Upgrade to macOS Sonoma 14.1
  5. For Apple Watch: Upgrade to watchOS 10.1
Caveat Standard OS upgrade considerations apply - review release notes for compatibility with critical apps and ensure backups before upgrading

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