CVE-2022-46720
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 · uneditedAn integer overflow was addressed with improved input validation. This issue is fixed in iOS 16.2 and iPadOS 16.2, macOS Ventura 13.1. An app may be able to break out of its sandbox
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 confidenceInteger overflow vulnerability in Apple iOS, iPadOS, and macOS that allowed a malicious application to escape its sandbox containment through improper input validation. Fixed by Apple in iOS 16.2, iPadOS 16.2, and macOS Ventura 13.1.
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.2< 16.2< 13.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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 iPhoneOpen Settings > General > About and look at the 'Software Version' fieldAffected if The version shown is less than 16.2 (for example, 16.1.2, 16.0, 15.x)
-
Check iPadOS version on iPadOpen Settings > General > About and look at the 'Software Version' fieldAffected if The version shown is less than 16.2 (for example, 16.1, 15.5, 15.4)
-
Check macOS version on MacClick the Apple menu > About This Mac, or open System Settings > AboutAffected if The macOS version shown is less than 13.1 (for example, 13.0, 12.x, 11.x)
-
Verify device type matches affected productConfirm whether the device is an iPhone (iOS), iPad (iPadOS), or Mac (macOS)Affected if The device runs iOS, iPadOS, or macOS and the version is below the fixed releases
A user is affected if their iPhone runs iOS below 16.2, their iPad runs iPadOS below 16.2, or their Mac runs macOS Ventura below 13.1.
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 by updating affected devices to iOS 16.2+/iPadOS 16.2+/macOS Ventura 13.1 or later.
iOS 16.2 / iPadOS 16.2 / macOS Ventura 13.1 or later
- For iOS/iPadOS: Go to Settings > General > Software Update, then download and install iOS 16.2 or iPadOS 16.2 or later
- For macOS: Go to System Settings (or System Preferences on older versions) > Software Update, then download and install macOS Ventura 13.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46720 — 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-46720 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