Apple Multiple Products Memory Corruption Vulnerability
Apple · Multiple Products
A memory corruption flaw in Apple's Multiple Products (affecting iOS, iPadOS and tvOS, as addressed in the vendor's update) stems from an out-of-bounds write in the vulnerable code, which was fixed by removing that code. An attacker with a local application can execute arbitrary code with kernel privileges, requiring no privileges beforehand but needing user interaction to trigger.
A memory corruption issue was addressed by removing the vulnerable code. This issue is fixed in iOS 13.6 and iPadOS 13.6, tvOS 13.4.8. An application may be able to execute arbitrary code with kernel privileges.
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 2/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 20 months after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+20 mo
- Added to CISA KEVEU database agrees+20 mo
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
2 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 2 cited passages 2ExecutionTA0002
requires user to open malicious app or file
A memory corruption issue was addressed by removing the vulnerable code
Privilege EscalationTA0004
kernel-level code execution grants privilege escalation
An application may be able to execute arbitrary code with kernel privileges
Detection
0 rules for this CVE · 70 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2020-9907 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Malicious FileT1204.00239 general rules
- Droppers Exploiting CVE-2017-11882criticalstable
- Ursnif Malware C2 URL Patterncriticalstable
- Exploit for CVE-2017-8759criticaltest
- Potential Maze Ransomware Activitycriticaltest
- File With Uncommon Extension Created By An Office Applicationhightest
- Flash Player Update from Suspicious Locationhightest
- GAC DLL Loaded Via Office Applicationshightest
- HackTool - LittleCorporal Generated Maldoc Injectionhightest
Exploitation for Privilege EscalationT106831 general rules
- Exploiting CVE-2019-1388criticalstable
- Audit CVE Eventcriticaltest
- HackTool - SysmonEOP Executioncriticaltest
- InstallerFileTakeOver LPE CVE-2021-41379 File Create Eventcriticaltest
- Possible Coin Miner CPU Priority Paramcriticaltest
- Potential CVE-2021-41379 Exploitation Attemptcriticaltest
- Potential SystemNightmare Exploitation Attemptcriticaltest
- Sudo Privilege Escalation CVE-2019-14287 - Builtincriticaltest
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
What security researchers reported
Not named in any threat report yetAlso mentioned in 50 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Actively_Exploited_Kev | Oct 29, 202628 Oct 2026
- Actively_Exploited_Kev | Oct 28, 202627 Oct 2026
- Actively_Exploited_Kev | Oct 27, 202626 Oct 2026
- Actively_Exploited_Kev | Oct 24, 202623 Oct 2026
- Actively_Exploited_Kev | Oct 23, 202622 Oct 2026
- Actively_Exploited_Kev | Oct 22, 202621 Oct 2026
- 44 more on OTX