CVE-2022-43454
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 · uneditedA double free issue was addressed with improved memory management. This issue is fixed in macOS Ventura 13.1, watchOS 9.2, iOS 16.2 and iPadOS 16.2, tvOS 16.2. 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 · high confidenceA double free vulnerability in the kernel of multiple Apple operating systems (macOS, iOS, iPadOS, watchOS, tvOS) that allowed a malicious application to achieve arbitrary code execution with kernel-level privileges. The issue was addressed through improved memory management in version 13.1/16.2/9.2 updates.
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< 16.2< 16.2< 13.1< 16.2< 9.2CVSS 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 macOS versionOpen System Settings (or System Preferences on older macOS), go to General > About, and note the version number listed next to 'macOS'Affected if The version shown is below 13.1 (for example, 13.0, 12.x, 11.x)
-
Check iOS versionOn the device, go to Settings > General > About, and note the version number next to 'iOS'Affected if The version shown is below 16.2 (for example, 16.1, 16.0, 15.x)
-
Check iPadOS versionOn the iPad, go to Settings > General > About, and note the version number next to 'iPadOS'Affected if The version shown is below 16.2 (for example, 16.1, 16.0, 15.x)
-
Check watchOS versionOn the Apple Watch, open the Settings app, go to General > About, and note the version. Alternatively, open the Watch app on a paired iPhone and check the watch's software version in General settingsAffected if The version shown is below 9.2 (for example, 9.1, 9.0, 8.x)
-
Check tvOS versionOn Apple TV, go to Settings > General > About, and note the version numberAffected if The version shown is below 16.2 (for example, 16.1, 16.0, 15.x)
If any Apple device runs an operating system version lower than 13.1 for macOS or 16.2 for iOS/iPadOS/tvOS (or 9.2 for watchOS), the device is affected by this kernel double-free vulnerability.
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 · scoped9.213.116.2
Apply the vendor-supplied security updates: macOS Ventura 13.1, iOS/iPadOS 16.2, watchOS 9.2, and tvOS 16.2. Prioritize updating devices with elevated privilege access or exposure to untrusted applications.
iOS 16.2, iPadOS 16.2, macOS 13.1 (Ventura), tvOS 16.2, watchOS 9.2
- For iPhone: Go to Settings > General > Software Update and install iOS 16.2 or later
- For iPad: Go to Settings > General > Software Update and install iPadOS 16.2 or later
- For Mac: Go to System Settings > General > Software Update and install macOS Ventura 13.1 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 16.2 or later
- For Apple Watch: On the iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 9.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43454 — 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-43454 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