CVE-2022-46701
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 · uneditedThe issue was addressed with improved bounds checks. This issue is fixed in iOS 16.2 and iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2. Connecting to a malicious NFS server may lead to arbitrary code execution with kernel 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 · high confidenceA bounds check vulnerability in the NFS client implementation in Apple operating systems allows a malicious NFS server to trigger a buffer overflow, leading to arbitrary code execution with kernel privileges.
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.0, < 16.2>= 16.0, < 16.2>= 13.0, < 13.1< 16.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 the installed iOS or iPadOS versionGo to Settings > General > About on the device and note the version number shown next to 'Version'Affected if The version is 16.0, 16.1, or any 16.x version prior to 16.2 (for example, 16.0.1, 16.1.1)
-
Check the installed macOS versionOpen Terminal and run 'sw_vers -productVersion' or go to System Settings > General > About and note the version numberAffected if The version is 13.0 or 13.0.x (Ventura initial release) - versions 13.1 and later are patched
-
Check the installed tvOS versionGo to Settings > General > About > Version on the Apple TV deviceAffected if The version is any tvOS version prior to 16.2 (for example, 16.0, 16.1, 16.1.1)
-
Verify if NFS client functionality is enabled on macOSIn Terminal, run 'ls /sbin/mount_nfs' to confirm the NFS client binary exists, and check for active NFS mounts using 'mount | grep nfs' or 'showmount -e localhost'Affected if The system has NFS client binary present and has mounted NFS shares or has NFS export configurations
You are affected if your device runs any of the affected OS versions (iOS/iPadOS 16.0-16.1, macOS 13.0-13.0.x, tvOS before 16.2) AND you have enabled or used the NFS client to connect to servers.
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 · scoped13.116.2
Apply vendor patches (iOS 16.2+, iPadOS 16.2+, macOS Ventura 13.1+, tvOS 16.2+) and avoid connecting to untrusted NFS servers until updates are deployed.
iOS 16.2/iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2
- Upgrade iPadOS to version 16.2 or later
- Upgrade iPhone OS to version 16.2 or later
- Upgrade macOS to Ventura 13.1 or later
- Upgrade tvOS to version 16.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-46701 — 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-2022-46701 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