IpadosOperating system · Apple

CVE-2022-32949

HIGH · 7.8 CVSS v3.1 Published 2023-02-27
Fix available
A fix is available. Upgrade to 15.7.1 / 16.0 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
This issue was addressed with improved checks. This issue is fixed in iOS 15.7.1 and iPadOS 15.7.1, tvOS 16. An app 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 · moderate confidence

A kernel privilege escalation vulnerability in iOS, iPadOS, and tvOS that allows a malicious application to execute arbitrary code with kernel-level privileges, bypassing the standard application sandbox. The issue was addressed with improved checks in the affected Apple operating systems.

MitigationUpdate affected devices to iOS 15.7.1/iPadOS 15.7.1 or later, or tvOS 16 or later, to apply Apple's security patches.

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.7.1
Iphone OsOperating system
Affected:< 15.7.1
TvosOperating system
Affected:< 16.0

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 your device type
    Determine if you are using an iPhone, iPad, or Apple TV. On the device, go to Settings > General > About to see the model name.
    Affected if Device is an iPhone, iPad, or Apple TV running iOS, iPadOS, or tvOS respectively
  2. Check iOS or iPadOS version on iPhone or iPad
    On iPhone or iPad, go to Settings > General > About and look at the 'Version' field. Note the full version number displayed (for example, 15.7 or 15.6.1).
    Affected if This check applies to iPhone and iPad devices. Continue to version comparison.
  3. Check tvOS version on Apple TV
    On Apple TV, go to Settings > General > About > Version. Note the software version displayed.
    Affected if This check applies only to Apple TV devices. Continue to version comparison.
  4. Compare installed version against affected ranges
    For iPhone/iPad: compare your installed iOS/iPadOS version to 15.7.1. For Apple TV: compare your installed tvOS version to 16.0. Use numeric version comparison where a lower version number indicates the update has not been applied.
    Affected if iOS or iPadOS version is below 15.7.1, or tvOS version is below 16.0 - indicating the security patch for CVE-2022-32949 has not been applied

Your device is affected by CVE-2022-32949 if it runs iOS or iPadOS version lower than 15.7.1, or tvOS version lower than 16.0, as these versions lack the improved kernel privilege escalation checks.

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 15.7.1 / 16.0 or later
Fixed in 15.7.116.0
Interim mitigation

Update affected devices to iOS 15.7.1/iPadOS 15.7.1 or later, or tvOS 16 or later, to apply Apple's security patches.

Recommended fix High confidence

iOS 15.7.1, iPadOS 15.7.1, tvOS 16

  1. Back up your device data before performing the update
  2. On iPhone or iPad: Go to Settings > General > Software Update and download/install iOS 15.7.1 or iPadOS 15.7.1
  3. On Apple TV: Go to Settings > System > Software Updates and download/install tvOS 16
  4. Ensure the device remains connected to power during the update process
  5. After updating, verify the version in Settings > General > About
Caveat Standard iOS/tvOS upgrade considerations apply - some older apps may become incompatible

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32949 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