CVE-2022-32793
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 · uneditedMultiple out-of-bounds write issues were addressed with improved bounds checking. This issue is fixed in macOS Monterey 12.5, watchOS 8.7, tvOS 15.6, iOS 15.6 and iPadOS 15.6. An app may be able to disclose kernel memory.
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 confidenceThis is a kernel memory disclosure vulnerability in Apple's operating systems involving multiple out-of-bounds write issues. An attacker who tricks a user into installing a malicious app could exploit these memory corruption flaws to read sensitive kernel memory contents due to insufficient bounds checking in the affected code paths.
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= 35= 36< 15.6< 15.6>= 12.0, < 12.5< 15.6< 8.7CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device or Fedora systemOn Apple devices: Settings > General > About shows the product name and version. On macOS: System Preferences > About. On Fedora: run 'cat /etc/fedora-release' in Terminal.Affected if Any Apple product or Fedora system listed in the affected products.
-
Check your iOS or iPadOS versionGo to Settings > General > About > Version. Compare the shown version number to the affected range.Affected if Version is lower than 15.6 (e.g., 15.5, 15.4, etc.)
-
Check your macOS versionClick Apple menu > About This Mac. Compare the macOS version to the affected range.Affected if Version is 12.0 through 12.4 (any version from 12.0 up to but not including 12.5)
-
Check your watchOS, tvOS versionOn Apple Watch: Open the Watch app on iPhone > General > About. On Apple TV: Go to Settings > General > About.Affected if watchOS is lower than 8.7, or tvOS is lower than 15.6
-
Check your Fedora versionRun 'cat /etc/fedora-release' or 'uname -r' in Terminal to get the kernel and OS version.Affected if Fedora version is exactly 35 or 36
-
Determine if third-party app installation is possibleOn iOS/iPadOS: Check if App Store access is enabled. On macOS: Check if apps from unidentified developers can be installed (System Preferences > Security & Privacy > General).Affected if Running a vulnerable OS version AND the device allows installation of apps from third-party sources (App Store, sideloading, or unidentified developers)
You are affected if your Apple device runs any version lower than the fixed releases (iOS/iPadOS 15.6, macOS 12.5, watchOS 8.7, tvOS 15.6) or if you run Fedora 35 or 36, and you have the ability to install applications on the 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.712.515.6
Apply the vendor-supplied security updates: macOS Monterey 12.5, watchOS 8.7, tvOS 15.6, iOS 15.6, or iPadOS 15.6. Organizations should prioritize patching mobile devices and endpoints that support sideloaded applications.
Apple devices: iOS 15.6+, iPadOS 15.6+, macOS 12.5+, watchOS 8.7+, tvOS 15.6+
- For iOS devices: Go to Settings > General > Software Update and upgrade to iOS 15.6 or later
- For iPadOS devices: Go to Settings > General > Software Update and upgrade to iPadOS 15.6 or later
- For macOS devices: Go to System Preferences > Software Update and upgrade to macOS Monterey 12.5 or later
- For Apple Watch: Go to Settings > General > Software Update on the watch and upgrade to watchOS 8.7 or later
- For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 15.6 or later
- After upgrading, verify the version in Settings to confirm the security update is applied
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-32793 — 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-32793 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