Threats / Apple / CVE-2020-9934
CVE-2020-9934
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Apple iOS, iPadOS, and macOS vulnerability
Apple iOS, iPadOS, and macOS contain an input validation vulnerability allowing local attackers to view sensitive user information.
Verdict
Today item — known-exploited.
A local input validation flaw in Apple operating systems enables unauthorized disclosure of sensitive user data. The vulnerability has been exploited in the wild, though with minimal predicted exploitation likelihood.
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
2 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 2022-09-08).
Probability (EPSS)
EPSS 0.03208 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Apple, iOS, iPadOS, and macOS. Confirm exact fixed builds in the vendor advisory.
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 gain local access to a target device running iOS, iPadOS, or macOS.
Business
An insider threat or compromised device creates exposure of user personal data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft malicious input to bypass the application's validation controls.
Business
Security controls designed to protect sensitive information are circumvented.
3
Lateral reach — past segmentation narrative 3
Attacker
I read sensitive user information that should be restricted from my access level.
Business
Confidential user data is disclosed, creating privacy breach and regulatory liability.
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