Threats / Apple / CVE-2020-27950
CVE-2020-27950
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Apple Multiple Products vulnerability
Apple iOS, iPadOS, macOS, and watchOS contain a memory initialization vulnerability allowing malicious applications to disclose kernel memory.
Verdict
Today item — known-exploited.
A memory initialization flaw in multiple Apple platforms enables local privilege escalation and information disclosure. Exploitation requires application execution on the target device and has been observed in active attacks.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
Probability (EPSS)
EPSS 0.1652 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, Multiple Products. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-665 Improper Initialization — weakness family: Resource / availability.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious application that exploits uninitialized memory regions to read kernel data structures.
Business
Kernel memory disclosure undermines platform security isolation and enables further exploitation chains.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract sensitive kernel pointers and ASLR offsets from disclosed memory to bypass address space layout randomization.
Business
Loss of memory protection mechanisms increases risk of privilege escalation and complete system compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage disclosed kernel information to craft targeted exploits against other kernel vulnerabilities or escalate application privileges.
Business
Attackers gain unauthorized access to user data, device functionality, and potential lateral movement across the ecosystem.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05