dbcve.org
IpadosOperating system · Apple

CVE-2022-42793

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 11.7 / 12.6 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
An issue in code signature validation was addressed with improved checks. This issue is fixed in macOS Big Sur 11.7, macOS Ventura 13, iOS 16, iOS 15.7 and iPadOS 15.7, macOS Monterey 12.6. An app may be able to bypass code signing 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 · moderate confidence

This is a code signing bypass vulnerability in Apple's macOS and iOS platforms. An application could potentially circumvent code signature validation checks, which are designed to verify the integrity and authenticity of executable code. This allows potentially malicious or tampered code to run without detection by the system's security mechanisms.

MitigationApply the security updates: macOS Big Sur 11.7 or later, macOS Monterey 12.6 or later, macOS Ventura 13 or later, iOS 15.7 or later, or iOS 16 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.7
Iphone OsOperating system
Affected:< 15.7
macOSOperating system
Affected:>= 11.0, < 11.7>= 12.0, < 12.6

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. Identify the operating system
    Determine if the system is running macOS or iOS/iPadOS. On macOS, check System Preferences > About or run 'sw_vers'. On iOS/iPadOS, check Settings > General > About.
    Affected if System is not applicable (this CVE only affects macOS and iOS/iPadOS)
  2. Check macOS version on Apple desktops/laptops
    Run 'sw_vers -productVersion' in Terminal or open System Preferences > About to view the macOS version number.
    Affected if Version is 11.0 through 11.6.x, or 12.0 through 12.5.x (vulnerable ranges)
  3. Check iOS/iPadOS version on Apple mobile devices
    Open Settings > General > About and note the version number, or connect to a computer and use iTunes/Finder to check the iOS version.
    Affected if Version is 15.0 through 15.6.x (vulnerable range)
  4. Verify the code signing subsystem is active
    This vulnerability exploits the code signing validation mechanism. On affected versions, the code signing bypass applies to any application attempting to run unsigned or tampered code. No specific configuration check needed - the vulnerability exists in the code signing validation logic itself.
    Affected if Running any application on a vulnerable OS version could potentially bypass code signature checks

A system is affected if it is running macOS 11.0-11.6.x or 12.0-12.5.x, or iOS/iPadOS 15.0-15.6.x - versions prior to the 15.7/11.7/12.6 security updates.

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 11.7 / 12.6 / 15.7 or later
Fixed in 11.712.615.7
Interim mitigation

Apply the security updates: macOS Big Sur 11.7 or later, macOS Monterey 12.6 or later, macOS Ventura 13 or later, iOS 15.7 or later, or iOS 16 or later.

Recommended fix High confidence

iOS 15.7+/iPadOS 15.7+/macOS 11.7+/macOS 12.6+/macOS Ventura 13+

  1. Identify the current OS version on the affected device
  2. For iPhone/iPad: Upgrade to iOS 15.7 or later (or iOS 16 if the device is supported)
  3. For iPadOS: Upgrade to iPadOS 15.7 or later
  4. For macOS Big Sur (11.x): Upgrade to macOS 11.7 or later
  5. For macOS Monterey (12.x): Upgrade to macOS 12.6 or later
  6. Alternatively, for macOS users whose hardware supports it, consider upgrading to macOS Ventura 13 or later
Caveat Some older devices may not support the latest OS versions and may require hardware replacement; upgrading to major OS versions may introduce UI changes

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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