CVE-2022-42827
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 · uneditedAn out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 15.7.1 and iPadOS 15.7.1, iOS 16.1 and iPadOS 16. An application may be able to execute arbitrary code with kernel privileges. Apple is aware of a report that this issue may have been actively exploited..
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 confidenceAn out-of-bounds write vulnerability in the iOS/iPadOS kernel that allows a malicious application to execute arbitrary code with kernel privileges. The issue was addressed with improved bounds checking and affects multiple iOS versions.
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< 15.7.1< 15.7.1>= 16.0, < 16.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the iOS or iPadOS version installed on the deviceOn the device, go to Settings > General > About and note the version number displayed next to 'Version'Affected if The version displayed is lower than 15.7.1, or is 16.0.x (any version in the 16.0 series before 16.1)
-
Verify the exact version number in the About screenIn Settings > General > About, read the full version number (for example, 15.6, 15.7, 16.0, 16.0.1)Affected if The version shows 15.7, 15.6.1, 15.5, 14.x or any version below 15.7.1, OR shows 16.0, 16.0.1, 16.0.2 (any 16.0.x version before 16.1)
-
Confirm the device model is an iPhone or iPadIn Settings > General > About, check the model name or model number to confirm the device is an Apple iPhone or iPad running iOS or iPadOSAffected if The device runs iOS or iPadOS (this vulnerability does not affect macOS, watchOS, or other platforms)
The device is affected if it runs any version of iOS or iPadOS below 15.7.1, or any version from 16.0 through 16.0.x (before 16.1). Devices running 15.7.1 and later, or 16.1 and later, are not affected.
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 · scoped15.7.116.1
Apply available security updates (iOS 15.7.1, iPadOS 15.7.1, iOS 16.1, iPadOS 16 or later) to all affected devices immediately, as this vulnerability is being actively exploited in the wild.
iOS 15.7.1 / iPadOS 15.7.1 or iOS 16.1 / iPadOS 16.1
- Back up your iPhone or iPad data using iCloud or iTunes/Finder before updating
- On the device, go to Settings > General > Software Update
- Download and install iOS 15.7.1 (for iPhone) or iPadOS 15.7.1 (for iPad), OR iOS 16.1/iPadOS 16.1 depending on which major version line you are on
- After installation, verify the update was successful by checking Settings > General > About > iOS Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42827 — 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-42827 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