Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2020-9934: Apple TCC bypass through environment-variable manipulation

Published Oct 16, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS3.2%88th percentile
CISA KEVYesAdded Sep 8, 2022
In the wildActivePer CISA KEV
Vendor
Apple
IdentifiersCVE-2020-9934CWE-73

CVE-2020-9934 is an environment-variable validation vulnerability that enables a local user to bypass Apple's Transparency, Consent, and Control (TCC) protections. In the documented macOS exploit, the per-user tccd daemon derives its authorization database location from the attacker-controllable HOME environment variable. Changing that variable and restarting the daemon redirects it to an attacker-controlled database outside the original database's System Integrity Protection (SIP) protections. The attacker can then insert authorization decisions that permit applications to access protected user data without consent prompts. Apple's affected-platform description includes iOS and iPadOS, while the technical writeup states that this particular TCC bypass applies only to macOS.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A local attacker can bypass TCC authorization checks and access sensitive user information without obtaining the user's consent. The demonstrated exploit granted an application access to the user's protected Documents folder. It also permits modification of authorization decisions in the redirected TCC database without modifying the original SIP-protected database.

Mitigation

If you can’t patch tonight, do this now.

Until the system is patched, restrict local access to trusted users only and monitor for unusual access to TCC-protected directories. No effective configuration-based mitigation is available due to the nature of the flaw.

Remediation

Patch, then assume compromise.

Install the applicable Apple update addressing CVE-2020-9934: macOS Catalina 10.15.6, Security Update 2020-004 for applicable macOS releases, or iOS/iPadOS 13.6. The fix improves validation of environment variables. Security Update 2020-004 was released on July 15, 2020.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
tccbypass.rbThis repository contains a single Metasploit post-exploitation module (modules/post/osx/escalate/tccbypass.rb) targeting macOS Catalina (versions 10.15.0 through 10.15.5) and exploiting CVE-2020-9934. The module leverages a vulnerability in the TCC (Transparency, Consent, and Control) daemon, allowing an attacker with local access to manipulate the TCC database by setting the HOME environment variable to a writable directory. The exploit creates a fake TCC database, restarts the TCC daemon to use this database, and inserts entitlements for various protected services (such as camera, microphone, screen capture, and file access) for the Terminal application. The module is operational and provides attackers with elevated access to sensitive macOS services. The code is written in Ruby and is designed to be run within the Metasploit framework. No network endpoints are involved; the attack vector is local privilege escalation via file and environment variable manipulation.Framework: metasploit · ruby · localWeaponizedCVE-2020-9934This repository is a Proof of Concept exploit for CVE-2020-9934, targeting macOS's TCC (Transparency, Consent, and Control) framework. The exploit is implemented in Swift and consists of two main code files: BypassTCC.swift, which contains the core logic for bypassing TCC protections, and main.swift, which demonstrates the exploit's capabilities. The exploit works by creating a fake TCC database in a temporary directory, granting all TCC entitlements to itself and Terminal.app, and then restarting the TCC daemon to apply these changes. The PoC then demonstrates its success by creating, reading, listing, and deleting a file in a TCC-protected directory, actions that would normally be restricted. The attack vector is local, requiring code execution on the target system. Several fingerprintable file paths are used, including the fake TCC database and the demo file. The exploit is a functional PoC and does not include weaponized or easily customizable payloads.mattshockl · Disclosed Jul 27, 2020 · swift · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMac Os Xoperating_system
FAQ

Frequently asked questions

Is CVE-2020-9934 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 8, 2022.
Is there a public exploit for CVE-2020-9934?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2020-9934, the earliest disclosed Jul 27, 2020.
Is there a patch for CVE-2020-9934?
Install the applicable Apple update addressing CVE-2020-9934: macOS Catalina 10.15.6, Security Update 2020-004 for applicable macOS releases, or iOS/iPadOS 13.6. The fix improves validation of environment variables.
What products are affected by CVE-2020-9934?
Apple Ipados, Apple Iphone Os, and Apple Mac Os X.
How severe is CVE-2020-9934?
CVE-2020-9934 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 3.2% (88th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.