LiveActive security incident?Get immediate response
CVE Record

CVE-2024-23296: A memory corruption issue was addressed with improved validation.

A memory corruption issue was addressed with improved validation. This issue is fixed in iOS 16.7.8 and iPadOS 16.7.8, iOS 17.4 and iPadOS 17.4, macOS Monterey 12.7.6, macOS Sonoma 14.4, macOS Ventura 13.6.7, tvOS 17.4, visionOS 1.1, watchOS 10.4. An attacker with arbitrary kernel read and write capability may be able to bypass kernel memory protections. Apple is aware of a report that this issue may have been exploited.

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-23296 is an Apple kernel-related memory corruption issue. If an attacker already has arbitrary kernel read and write capability, they may bypass kernel memory protections. Apple fixed it across iOS, iPadOS, macOS, tvOS, visionOS, and watchOS, and CISA lists it as known exploited.

Executive priority

Treat this as a high-priority Apple fleet patching item. The vulnerability has high technical impact and KEV evidence of exploitation, but the attack requires prior kernel-level capability, so urgency is strongest where devices face elevated targeting risk.

Technical view

The issue is CWE-787 out-of-bounds write/memory corruption, addressed by Apple with improved validation. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely in organizations running Apple endpoints or devices below the fixed releases: iOS/iPadOS 16.7.8 or 17.4, macOS Monterey 12.7.6, Ventura 13.6.7, Sonoma 14.4, tvOS 17.4, visionOS 1.1, or watchOS 10.4.

Exploitation context

Apple reported the issue may have been exploited, and CISA includes CVE-2024-23296 in its Known Exploited Vulnerabilities catalog. The provided sources do not include public exploit details, observed campaigns, or weaponization guidance.

Researcher notes

The bundle provides limited root-cause detail beyond memory corruption and improved validation. Analysis should avoid assuming standalone remote compromise. Focus validation on vulnerable OS versions, patch state, and whether other vulnerabilities could provide the prerequisite kernel read/write capability.

Mitigation direction

  • Update affected Apple devices to the fixed versions or later.
  • Prioritize internet-facing, executive, admin, and high-risk user devices.
  • Use MDM reporting to identify devices below the fixed Apple releases.
  • Check Apple advisories for product-specific update availability and constraints.
  • Track CISA KEV remediation deadlines where applicable.

Validation and detection

  • Inventory Apple device OS versions across managed and unmanaged fleets.
  • Confirm devices report fixed versions or later after update deployment.
  • Review MDM compliance data for failed, deferred, or blocked updates.
  • Check whether legacy devices cannot receive the fixed releases.
  • Monitor Apple and CISA references for revised guidance.
Prepared
Confidence
high
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-23296 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
19Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-23296Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AppleiOS and iPadOS0, 0Listed
ApplemacOS0, 0, 0Listed
AppletvOS0Listed
ApplevisionOS0Listed
ApplewatchOS0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.