CVE-2025-31277

Apple Multiple Products Buffer Overflow Exploitation (CVE-2025-31277)

Detects potential exploitation of CVE-2025-31277, a buffer overflow vulnerability (CWE-119) affecting multiple Apple products. This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild. Successful exploitation may allow attackers to execute arbitrary code, escalate privileges, or cause denial of service on affected Apple devices and systems.

Vulnerability Intelligence

KEV — Known Exploited

What is CVE-2025-31277 Apple Multiple Products Buffer Overflow Exploitation (CVE-2025-31277)?

Apple Multiple Products Buffer Overflow Exploitation (CVE-2025-31277) (CVE-2025-31277) maps to the Execution and Privilege Escalation and Defense Evasion tactics — the adversary is trying to run malicious code in MITRE ATT&CK.

This page provides production-ready detection logic for Apple Multiple Products Buffer Overflow Exploitation (CVE-2025-31277), covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, Microsoft Sentinel, macOS EDR telemetry. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Execution Privilege Escalation Defense Evasion
Microsoft Sentinel / Defender
kusto
let suspiciousAppleProcs = dynamic(["mdmclient", "mobileassetd", "softwareupdated", "nsurlsessiond", "trustd", "accountsd", "apsd"]);
let timeWindow = 1h;
union DeviceProcessEvents, DeviceEvents
| where Timestamp > ago(timeWindow)
| where DeviceType in ("Mac", "iOS") or OSPlatform has_any ("macOS", "iOS", "iPadOS")
| where (ActionType in ("ProcessCreated", "ProcessCrashed", "ExceptionThrown") and FileName in~ (suspiciousAppleProcs))
    or (ActionType == "ProcessCrashed" and ProcessCommandLine has_any ("overflow", "heap", "stack", "corrupt"))
    or (ActionType == "ProcessCreated" and InitiatingProcessFileName in~ (suspiciousAppleProcs) and FileName in~ ("sh", "bash", "zsh", "python3", "perl", "ruby"))
| extend RiskScore = case(
    ActionType == "ProcessCrashed" and FileName in~ (suspiciousAppleProcs), 90,
    ActionType == "ProcessCreated" and InitiatingProcessFileName in~ (suspiciousAppleProcs) and FileName in~ ("sh", "bash", "zsh"), 85,
    70
  )
| where RiskScore >= 70
| project Timestamp, DeviceName, DeviceId, AccountName, ActionType, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, RiskScore
| sort by RiskScore desc, Timestamp desc

Identifies suspicious process behavior on Apple devices consistent with CVE-2025-31277 buffer overflow exploitation, including process crashes of Apple system daemons and unexpected shell spawning from Apple system processes.

high severity medium confidence

Data Sources

Microsoft Defender for Endpoint Microsoft Sentinel macOS EDR telemetry

Required Tables

DeviceProcessEvents DeviceEvents

False Positives

  • Legitimate Apple software update processes may trigger process restarts that resemble crashes
  • Developer tools and Xcode build processes may spawn shells from system daemons during testing
  • Third-party security tools performing system scans may cause transient process anomalies
  • Beta macOS or iOS software installations may exhibit unstable daemon behavior unrelated to exploitation

Sigma rule & cross-platform mapping

The detection logic for Apple Multiple Products Buffer Overflow Exploitation (CVE-2025-31277) (CVE-2025-31277) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: process_creation
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate Apple System Daemon Crash with Non-Zero Exit

    Expected signal: Process crash event for 'trustd' (or mock process) with SIGSEGV signal, non-zero exit code, and EXC_BAD_ACCESS exception type visible in /Library/Logs/DiagnosticReports/ and EDR crash telemetry

  2. Test 2Spawn Shell from Apple Daemon Context (Post-Exploitation Simulation)

    Expected signal: ProcessCreate event showing bash spawning /tmp/daemon_spawn_test.sh, with subsequent child processes for whoami, uname, id, and ls commands — EDR should record full process ancestry and command lines

  3. Test 3Generate Crash Report Artifact for Apple Daemon

    Expected signal: File creation event in ~/Library/Logs/DiagnosticReports/ for trustd crash file; log collection agents (Elastic Agent, CrowdStrike) should ingest the .crash file and surface EXC_BAD_ACCESS exception type in SIEM

Unlock Pro Content

Get the full detection package for CVE-2025-31277 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections