{"id":29428,"date":"2020-07-03T16:43:09","date_gmt":"2020-07-03T20:43:09","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=29428"},"modified":"2021-07-06T17:00:26","modified_gmt":"2021-07-06T21:00:26","slug":"mount_apfs-tcc-bypass-and-privilege-escalation","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/07\/03\/mount_apfs-tcc-bypass-and-privilege-escalation\/","title":{"rendered":"mount_apfs TCC Bypass and Privilege Escalation"},"content":{"rendered":"

Csaba Fitzl<\/a> (tweet<\/a>):<\/p>\n

We could mount the entire file system through APFS snapshots as read-only, with the noowners<\/code> flag, which enables us accessing (almost) every file in the file system, including data (documents, files, etc…) of every user on the system, including those protected by Apple’s privacy framework (TCC). Even with the Guest account we could read files of admin accounts as Guest! 😱<\/p>\n

[…]<\/p>\n

At the beginning of March 2020, Apple said that the fix is shipped in Catalina 10.15.4 beta, they didn’t tell a word how they fixed it. I quickly jumped on it, and I found that the trick still works. I was puzzled. After some testing it turned out that they tied this to the Full Disk Access (FDA) right in TCC (kTCCServiceSystemPolicyAllFiles<\/code>), which I found wrong.<\/p>\n<\/blockquote>\n

As he explains:<\/p>\n

\n

This still violates the basic BSD security model, as you can read other user’s file, without elevating to root. […] Even if SIP is ON and Terminal has Full Disk Access, you can’t see other user’s files with it - with this vulnerability you can.<\/p>\n<\/blockquote>\n

But Apple still considers it to be fixed.<\/p>\n\n

Thomas Reed<\/a>:<\/p>\n

Absolutely ridiculous fix, I agree. Gating the fix behind a gate that most people will have open is bad. Of course, FDA for Terminal is just bad in general, yet there’s no good way for technical users to NOT give FDA to Terminal. 😞<\/p>\n

It’s like Apple has designed TCC in such a way that you have to make an insecure config change to get real work done, but they can say, “Well, you would have been safe if you hadn’t made an insecure config change.” 😒<\/p>\n<\/blockquote>\n\n

And there are lots of other apps that needs Full Disk Access, for one reason<\/a> or another, but they shouldn’t be given access to other users’ files.<\/p>\n\n

Previously:<\/p>\n