dbcve.org
IpadosOperating system · Apple

CVE-2022-22663

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-26
Fix available
A fix is available. Upgrade to 10.15.7 / 11.6.5 or later.
See remediation →
58/100
Remediation priority · Elevated
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
This issue was addressed with improved checks to prevent unauthorized actions. This issue is fixed in iOS 15.4 and iPadOS 15.4, Security Update 2022-004 Catalina, macOS Monterey 12.3, macOS Big Sur 11.6.6. A malicious application may bypass Gatekeeper checks.

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

This is a Gatekeeper bypass vulnerability in macOS and iOS. A malicious application could circumvent Gatekeeper security checks that normally verify applications are from identified developers and have not been tampered with, potentially enabling arbitrary code execution with user interaction.

MitigationApply the available security updates: iOS 15.4, iPadOS 15.4, macOS Monterey 12.3, macOS Big Sur 11.6.6, or Security Update 2022-004 Catalina.

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.0, < 11.6.5>= 12.0.0, < 12.3

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

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

  1. Check macOS version on Mac
    Open Terminal and run: sw_vers -productVersion
    Affected if The version is 10.15.x (any version up to and including 10.15.7), 11.0 to 11.6.4, or 12.0 to 12.2
  2. Check iOS or iPadOS version
    On the device, go to Settings > General > About and note the version number
    Affected if The version is 15.x where x is less than 4 (such as 15.3, 15.2, 15.1, 15.0)
  3. Confirm Gatekeeper is enabled
    In Terminal, run: spctl --status. Gatekeeper should be enabled by default on unpatched systems.
    Affected if Gatekeeper is enabled (master-enable) and the OS version falls within the affected ranges listed above

You are affected if your macOS version is 10.15.x through 10.15.7, 11.0 through 11.6.4, or 12.0 through 12.2; or if your iOS/iPadOS version is 15.3 or earlier.

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 10.15.7 / 11.6.5 / 12.3 or later
Fixed in 10.15.711.6.512.3
Interim mitigation

Apply the available security updates: iOS 15.4, iPadOS 15.4, macOS Monterey 12.3, macOS Big Sur 11.6.6, or Security Update 2022-004 Catalina.

Recommended fix High confidence

iOS/iPadOS 15.4+ | macOS Catalina 10.15.7+ | macOS Big Sur 11.6.6+ | macOS Monterey 12.3+

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 15.4 or later
  2. For macOS Catalina (10.15.x): Go to System Preferences > Software Update and install version 10.15.7, or apply Security Update 2022-004 Catalina
  3. For macOS Big Sur (11.x): Go to System Preferences > Software Update and install version 11.6.6 or later
  4. For macOS Monterey (12.x): Go to System Preferences > Software Update and install version 12.3 or later
  5. After updating, verify Gatekeeper is enabled by running: sudo spctl --master-enable
Caveat Standard OS update risks apply - review release notes for app compatibility changes before updating production systems

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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