CVE-2023-42942
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 · uneditedThis issue was addressed with improved handling of symlinks. This issue is fixed in watchOS 10.1, macOS Sonoma 14.1, tvOS 17.1, iOS 16.7.2 and iPadOS 16.7.2, iOS 17.1 and iPadOS 17.1, macOS Ventura 13.6.1. A malicious app may be able to gain root privileges.
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 confidenceA symlink handling vulnerability in multiple Apple operating systems allows a malicious application to escalate privileges to root. The issue was addressed with improved symlink handling logic in the affected OS versions.
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< 16.7.2= 17.0< 16.7.2= 17.0>= 13.0, < 13.6.1= 14.0<= 17.1< 10.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneOn the iPhone, go to Settings > General > About and note the version number. Alternatively, use Xcode or a mobile device management (MDM) solution to query the iOS version programmatically.Affected if The installed version is less than 16.7.2 or equals 17.0
-
Check iPadOS version on iPadOn the iPad, go to Settings > General > About and note the version number. Alternatively, use Xcode or a mobile device management (MDM) solution to query the iPadOS version programmatically.Affected if The installed version is less than 16.7.2 or equals 17.0
-
Check macOS version on MacOpen Terminal and run 'sw_vers -productVersion' to retrieve the macOS version number.Affected if The installed version is 13.0 through 13.6.0 (any version >= 13.0 but < 13.6.1) or equals 14.0
-
Check watchOS version on Apple WatchOn the Apple Watch, go to Settings > General > About and note the version. Alternatively, check via the Watch app on a paired iPhone under My Watch > General > About, or use Apple Configurator or MDM.Affected if The installed version is less than 10.1
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About to view the tvOS version. Alternatively, use Xcode, Apple Configurator, or MDM to query the version remotely.Affected if The installed version is 17.1 or lower (any version <= 17.1)
If the device runs any iOS, iPadOS, macOS, watchOS, or tvOS version that falls within the ranges listed in the affected products, the environment is vulnerable to this symlink privilege escalation flaw.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.113.6.116.7.2
Apply the available security updates for the affected Apple operating systems (iOS 16.7.2/17.1, iPadOS 16.7.2/17.1, macOS Ventura 13.6.1/Sonoma 14.1, watchOS 10.1, tvOS 17.1).
iOS 16.7.2+/iPadOS 16.7.2+, iOS 17.1+/iPadOS 17.1+, macOS Ventura 13.6.1+, macOS Sonoma 14.1+, tvOS 17.1+, watchOS 10.1+
- Identify the affected Apple device (iPhone, iPad, Mac, Apple Watch, Apple TV)
- Determine the current installed OS version via Settings > General > About (iOS/iPadOS) or System Settings/About This Mac (macOS)
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS 16.7.2 or later, or iOS 17.1/iPadOS 17.1
- For Mac: Go to System Settings > General > Software Update and install macOS Ventura 13.6.1 or macOS Sonoma 14.1
- For Apple Watch: On iPhone, open Watch app > General > Software Update and install watchOS 10.1
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.1
- After updating, verify the new OS version is installed and confirm the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42942 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-42942 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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