CVE-2022-22632
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 · uneditedA logic issue was addressed with improved state management. This issue is fixed in tvOS 15.4, iOS 15.4 and iPadOS 15.4, macOS Big Sur 11.6.5, watchOS 8.5, macOS Monterey 12.3. A malicious application may be able to elevate 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 confidenceThis is a logic vulnerability in Apple's state management within iOS, iPadOS, macOS, tvOS, and watchOS. A malicious application can exploit improper state handling to elevate privileges beyond what should be permitted, potentially gaining root or kernel-level access.
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< 15.4< 15.4>= 11.6, < 11.6.5>= 12.0, < 12.3< 15.4< 8.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify your Apple device platformDetermine whether the device runs iOS, iPadOS, macOS, tvOS, or watchOS. On iOS/iPadOS, go to Settings > General > About. On macOS, go to Apple menu > About This Mac. On tvOS/watchOS, go to Settings > General > About.Affected if Any device running one of the affected platforms listed in the CVE.
-
Check your installed iOS or iPadOS versionOn iOS/iPadOS: Settings > General > About, then note the version number. Compare it to 15.4.Affected if iOS or iPadOS version is lower than 15.4.
-
Check your installed macOS versionOn macOS: Apple menu > About This Mac, then note the version number. Compare to 11.6.5 and 12.3. Check both the major version (e.g., 11.x or 12.x) and the specific subversion.Affected if macOS is 11.6.x (where x is less than 5) OR macOS is 12.0 through 12.2.x.
-
Check your installed tvOS or watchOS versionOn tvOS: Settings > General > About > Version. On watchOS: On iPhone, open Watch app > My Watch > General > About > watchOS. Compare to 15.4 for tvOS or 8.5 for watchOS.Affected if tvOS is lower than 15.4, or watchOS is lower than 8.5.
-
Assess application execution riskDetermine if the device allows installation of applications from untrusted sources. On iOS/iPadOS, check if sidloading, beta profiles, or developer modes are enabled. On macOS, check if Gatekeeper is disabled or if apps can be run from unidentified developers (System Preferences > Security & Privacy > General).Affected if The device allows execution of untrusted or unverified applications, enabling the malicious app attack vector for this privilege escalation.
You are affected if your device runs any version of iOS, iPadOS, macOS, tvOS, or watchOS that falls below the patched versions (15.4 for iOS/iPadOS/tvOS, 8.5 for watchOS, 11.6.5 or 12.3 for macOS) AND you have the potential for untrusted applications to execute on your device.
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 · scoped8.511.6.512.3
Apply the vendor-supplied patches by updating all affected Apple devices to tvOS 15.4, iOS/iPadOS 15.4, macOS Big Sur 11.6.5, macOS Monterey 12.3, or watchOS 8.5 respectively.
iOS 15.4 / iPadOS 15.4 / macOS Big Sur 11.6.5 / macOS Monterey 12.3 / tvOS 15.4 / watchOS 8.5
- Open Settings on the device
- Navigate to General > Software Update
- Download and install the latest available update for your device model
- For macOS: Use System Preferences > Software Update or the App Store to install macOS updates
- Restart the device after update installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22632 — 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-22632 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