dbcve.org
Ipad OsOperating system · Apple

CVE-2023-42836

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 12.7.2 / 13.6.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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
A logic issue was addressed with improved checks. This issue is fixed in iOS 17.1 and iPadOS 17.1, macOS Ventura 13.6.3, macOS Sonoma 14.1, macOS Monterey 12.7.2. An attacker may be able to access connected network volumes mounted in the home directory.

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

A logic flaw in the access control checks on Apple platforms allowed unauthorized access to network volumes mounted within the user's home directory. An attacker with local or adjacent network access could potentially bypass the intended authorization and read sensitive data from mounted network shares that should have been protected.

MitigationApply the vendor-provided security updates: iOS 17.1 and iPadOS 17.1 for mobile devices; macOS Ventura 13.6.3, macOS Sonoma 14.1, or macOS Monterey 12.7.2 for Mac systems.

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:>= 12.0, < 12.7.2>= 13.0, < 13.6.3= 14.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 macOS version
    Run 'sw_vers' in Terminal or go to System Settings > General > About > Version. Compare the version number to the affected ranges: 12.0 to 12.7.2, 13.0 to 13.6.3, or exactly 14.0.
    Affected if The installed version falls within any of these ranges: 12.0 <= version < 12.7.2, 13.0 <= version < 13.6.3, or version equals 14.0
  2. Check iOS or iPadOS version
    On the device, go to Settings > General > About > Version. Compare the version number to the affected range.
    Affected if The version is earlier than 17.1 (for iOS or iPadOS)
  3. Identify network volumes mounted in home directory
    Open Terminal and run 'mount | grep -E "smb|nfs|afp"' to list network-mounted volumes, or manually inspect the ~/Desktop, ~/Library/Volumes, or root-level /Volumes folder for network shares.
    Affected if Network volumes (SMB, NFS, AFP, or other network protocols) are mounted within the user's home directory or accessible via the system
  4. Verify mount points are within protected scope
    Check if any mounted network shares have paths that resolve to locations under the user's home directory (such as /Users/username/NetworkVolume or similar configurations).
    Affected if Network volumes are mounted in or under the user's home directory path (e.g., /Users/<username>/)

You are affected if your device runs an unpatched version (iOS/iPadOS < 17.1, macOS 12.0-12.7.2, 13.0-13.6.3, or exactly 14.0) AND you have network volumes mounted within your home directory.

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 12.7.2 / 13.6.3 / 17.1 or later
Fixed in 12.7.213.6.317.1
Interim mitigation

Apply the vendor-provided security updates: iOS 17.1 and iPadOS 17.1 for mobile devices; macOS Ventura 13.6.3, macOS Sonoma 14.1, or macOS Monterey 12.7.2 for Mac systems.

Recommended fix High confidence

iOS 17.1 / iPadOS 17.1 / macOS Monterey 12.7.2 / macOS Ventura 13.6.3 / macOS Sonoma 14.1

  1. For iPhone and iPad devices: Go to Settings > General > Software Update and upgrade to iOS 17.1 or iPadOS 17.1
  2. For macOS Monterey (12.x) users: Go to System Settings > General > Software Update and upgrade to macOS Monterey 12.7.2
  3. For macOS Ventura (13.x) users: Go to System Settings > General > Software Update and upgrade to macOS Ventura 13.6.3
  4. For macOS Sonoma (14.0) users: Go to System Settings > General > Software Update and upgrade to macOS Sonoma 14.1
  5. After updating, verify the update was successful by checking the OS version in Settings/About
Caveat Standard iOS/macOS upgrade considerations apply - ensure backups exist before updating

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

Fix this in Ipad Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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