dbcve.org
IpadosOperating system · Apple

CVE-2022-22613

HIGH · 7.8 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 8.5 / 10.15.7 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.4, iOS 15.4 and iPadOS 15.4, macOS Big Sur 11.6.5, Security Update 2022-003 Catalina, watchOS 8.5, macOS Monterey 12.3. An application may be able to execute arbitrary code 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 confidence

A kernel-level out-of-bounds write vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS) that allows a malicious application to write data outside allocated memory bounds and achieve arbitrary code execution with kernel privileges.

MitigationApply the relevant security update for the affected platform: iOS 15.4+, iPadOS 15.4+, macOS Monterey 12.3+, macOS Big Sur 11.6.5+, Security Update 2022-003 for Catalina, tvOS 15.4+, or watchOS 8.5+ as appropriate.

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
IpadosOperating system
Affected:< 15.4
Iphone OsOperating system
Affected:< 15.4
Mac Os XOperating system
Affected:>= 10.15, < 10.15.7= 10.15.7
macOSOperating system
Affected:>= 11.6, < 11.6.5>= 12.0, < 12.3= 10.15.7
TvosOperating system
Affected:< 15.4
WatchosOperating system
Affected:< 8.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version on iPhone
    On the iPhone, go to Settings > General > About and note the version number under 'Version'
    Affected if the version is less than 15.4 (for example, 15.3.1, 15.3, 15.2, etc.)
  2. Check iPadOS version on iPad
    On the iPad, go to Settings > General > About and note the version number under 'Version'
    Affected if the version is less than 15.4
  3. Check macOS version on Mac
    On Mac, click the Apple menu > About This Mac and note the version shown (for example, 12.2, 11.6, 10.15.7)
    Affected if the version is 10.15.7, or between 10.15.0 and 10.15.6, or between 11.6.0 and 11.6.4, or between 12.0.0 and 12.2.x (any version from 12.0 up to but not including 12.3)
  4. Check tvOS version on Apple TV
    On Apple TV, go to Settings > General > About and note the version number
    Affected if the version is less than 15.4
  5. Check watchOS version on Apple Watch
    On Apple Watch, open the Settings app, go to General > About and note the version number; or pair with iPhone and check in the Watch app under My Watch > General > About
    Affected if the version is less than 8.5

A user is affected if their device runs any iOS, iPadOS, macOS, tvOS, or watchOS version that falls within the vulnerable ranges specified (below 15.4 for iOS/iPadOS/tvOS/watchOS, or the specific macOS ranges for Catalina, Big Sur, and Monterey).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.5 / 10.15.7 / 11.6.5 or later
Fixed in 8.510.15.711.6.5
Interim mitigation

Apply the relevant security update for the affected platform: iOS 15.4+, iPadOS 15.4+, macOS Monterey 12.3+, macOS Big Sur 11.6.5+, Security Update 2022-003 for Catalina, tvOS 15.4+, or watchOS 8.5+ as appropriate.

Recommended fix High confidence

iOS 15.4 / iPadOS 15.4 / macOS Big Sur 11.6.5 / macOS Monterey 12.3 / tvOS 15.4 / watchOS 8.5 (or Security Update 2022-003 for macOS Catalina)

  1. Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
  2. Check the current installed OS version in Settings > General > About (iOS/iPadOS) or System Preferences > About (macOS)
  3. For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 15.4 or later
  4. For Mac: Go to System Preferences > Software Update and install the appropriate security update (macOS Big Sur 11.6.5, Security Update 2022-003 Catalina, or macOS Monterey 12.3)
  5. For Apple TV: Go to Settings > System > Software Updates and install tvOS 15.4
  6. For Apple Watch: On iPhone, open Watch app, go to My Watch > General > Software Update and install watchOS 8.5
  7. Verify the update was successfully installed by checking the OS version again
Caveat Standard OS security updates typically have minimal risk; verify critical applications are compatible before updating production devices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22613 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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