dbcve.org
IpadosOperating system · Apple

CVE-2022-22584

HIGH · 7.8 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 8.4 / 12.2 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
A memory corruption issue was addressed with improved validation. This issue is fixed in tvOS 15.3, iOS 15.3 and iPadOS 15.3, watchOS 8.4, macOS Monterey 12.2. Processing a maliciously crafted file may lead to arbitrary code execution.

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 confidence

Memory corruption vulnerability in Apple iOS, iPadOS, tvOS, watchOS, and macOS allows arbitrary code execution when processing a maliciously crafted file. The issue was addressed through improved validation in versions 15.3/8.4/12.2 or later.

MitigationUpdate affected Apple devices to iOS 15.3, iPadOS 15.3, tvOS 15.3, watchOS 8.4, or macOS Monterey 12.2 or later.

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.3
Iphone OsOperating system
Affected:< 15.3
macOSOperating system
Affected:< 12.2
TvosOperating system
Affected:< 15.3
WatchosOperating system
Affected:< 8.4

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. Identify the Apple operating system
    Determine 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 The device runs any of the affected products: iOS, iPadOS, macOS, tvOS, or watchOS.
  2. Check the installed version number
    Note the exact version number displayed in the About screen. For iOS/iPadOS and tvOS/watchOS, note both the version number and build number if shown. For macOS, note the version (e.g., 12.1, 12.0) and build number.
    Affected if The installed version is shown on the device.
  3. Compare against affected version thresholds
    For iOS or iPadOS: affected if version is below 15.3. For macOS: affected if version is below 12.2 (Monterey). For tvOS: affected if version is below 15.3. For watchOS: affected if version is below 8.4.
    Affected if The installed version is iOS < 15.3, iPadOS < 15.3, macOS < 12.2, tvOS < 15.3, or watchOS < 8.4.
  4. Confirm file processing capability
    The vulnerability triggers when processing a maliciously crafted file. This is a default capability on these Apple operating systems - users can typically open files from email, browsers, or other sources.
    Affected if The device can receive and open files from external sources, which is the default state for iOS, iPadOS, macOS, tvOS, and watchOS.

The environment is affected if the device runs an unpatched version of iOS, iPadOS, macOS, tvOS, or watchOS below the fixed releases (15.3, 15.3, 12.2, 15.3, or 8.4 respectively) and can process untrusted files, which is the default configuration.

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.4 / 12.2 / 15.3 or later
Fixed in 8.412.215.3
Interim mitigation

Update affected Apple devices to iOS 15.3, iPadOS 15.3, tvOS 15.3, watchOS 8.4, or macOS Monterey 12.2 or later.

Recommended fix High confidence

iOS 15.3/iPadOS 15.3, macOS Monterey 12.2, tvOS 15.3, watchOS 8.4

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 15.3 or later / iPadOS 15.3 or later
  2. For Mac: Go to System Preferences > Software Update and install macOS Monterey 12.2 or later
  3. For Apple TV: Go to Settings > System > Software Updates and install tvOS 15.3 or later
  4. For Apple Watch: On your iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 8.4 or later
Caveat Major OS version upgrade - review app compatibility before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22584 — 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-22584 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