dbcve.org
SafariWeb browser · Apple

CVE-2022-32923

MEDIUM · 6.5 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 9.1 / 13.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
A correctness issue in the JIT was addressed with improved checks. This issue is fixed in tvOS 16.1, iOS 15.7.1 and iPadOS 15.7.1, macOS Ventura 13, watchOS 9.1, Safari 16.1, iOS 16.1 and iPadOS 16. Processing maliciously crafted web content may disclose internal states of the app.

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 correctness flaw in Apple's JavaScriptCore JIT (Just-In-Time) compiler allows specially crafted web content to leak internal application states. This is an information disclosure vulnerability where processing malicious web pages may expose sensitive internal data through the JIT compiler's improper state handling.

MitigationApply the vendor-provided security updates (iOS 15.7.1/16.1, iPadOS 15.7.1/16.1, macOS Ventura 13, watchOS 9.1, tvOS 16.1, Safari 16.1) to all affected devices to address the JIT compiler vulnerability.

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
SafariWeb browser
Affected:< 16.1
IpadosOperating system
Affected:< 15.7.1
Iphone OsOperating system
Affected:< 15.7.1= 16.0
macOSOperating system
Affected:< 13.0
TvosOperating system
Affected:< 16.1
WatchosOperating system
Affected:< 9.1

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 Apple device and operating system
    Determine whether the system is macOS, iOS, iPadOS, tvOS, or watchOS, and note the specific OS version from the device settings (e.g., Settings > General > About on iOS/iPadOS; System Preferences > About on macOS; Settings > General on tvOS/watchOS).
    Affected if The OS version falls below the fixed versions: macOS < 13.0, iOS < 15.7.1 or = 16.0, iPadOS < 15.7.1, tvOS < 16.1, watchOS < 9.1.
  2. Check the Safari version if applicable
    Open Safari, then go to Safari > About Safari (macOS) or Settings > Safari > About (iOS/iPadOS) to view the Safari version number.
    Affected if Safari version is less than 16.1.
  3. Confirm JavaScript and JIT compilation are enabled
    Verify that JavaScript is enabled in the browser settings (Safari > Settings > Security > Enable JavaScript) and that JIT compilation is active, as the vulnerability requires the JIT compiler to process malicious web content.
    Affected if JavaScript is enabled and the JIT compiler is active (default state), which is required for the exploit to trigger.
  4. Verify WebKit usage by any applications
    Check if any third-party applications or browsers use WebKit (the rendering engine containing JavaScriptCore) by reviewing the application's user agent or about pages, as these would also be affected.
    Affected if Any app uses WebKit for rendering web content and processes untrusted web pages.

The environment is affected if the device runs any of the listed Apple OS versions below the fixed releases (macOS < 13.0, iOS/iPadOS < 15.7.1 or = 16.0, tvOS < 16.1, watchOS < 9.1) or Safari < 16.1, with JavaScript and the JIT compiler enabled (default).

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 9.1 / 13.0 / 15.7.1 or later
Fixed in 9.113.015.7.1
Interim mitigation

Apply the vendor-provided security updates (iOS 15.7.1/16.1, iPadOS 15.7.1/16.1, macOS Ventura 13, watchOS 9.1, tvOS 16.1, Safari 16.1) to all affected devices to address the JIT compiler vulnerability.

Recommended fix High confidence

iOS 15.7.1/16.1+, iPadOS 15.7.1/16+, macOS Ventura 13.0+, watchOS 9.1+, tvOS 16.1+, Safari 16.1+

  1. Back up all important data on the affected device before updating
  2. For iOS/iPadOS: Go to Settings > General > Software Update and install the available update to iOS/iPadOS 15.7.1 or later (iOS 16.1/iPadOS 16 recommended)
  3. For macOS: Go to System Preferences > Software Update and install macOS Ventura 13.0 or later
  4. For watchOS: Open the Watch app on iPhone, go to General > Software Update and install watchOS 9.1 or later
  5. For tvOS: Go to Settings > System > Software Updates and install tvOS 16.1 or later
  6. For Safari: Safari updates are included with macOS updates; ensure macOS is updated to 13.0 or later
Caveat Standard Apple security update - minimal risk; may require device restart

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

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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