macOS 'Quick Look' Bug Can Leak Encrypted Data Through Thumbnail Caches

[MacRumors]

A long-standing bug in macOS's Quick Look feature has the potential to expose sensitive user files like photo thumbnails and the text of documents, even on encrypted drives, according to security researchers.

Details on the Quick Look flaw were shared earlier this month by security researcher Wojciech Regula and over the weekend on security researcher Patrick Wardle's blog (via The Hacker News).

Image via Wojciech Regula​

Quick Look in macOS is a convenient Finder feature that's designed to present a zoomed-in view when you press the space bar on a photo or document that's selected.

To provide this preview functionality, Quick Look creates an unencrypted thumbnail database where thumbnails of files are kept, with the database storing file previews from a Mac's storage and any attached USB drives whenever a folder is opened. These thumbnails, which provide previews of content on an encrypted drive, can be accessed by someone with the technical know how and there's no automatic cache clearing that deletes them. As Regula explains:

It means that all photos that you have previewed using space (or Quicklook cached them independently) are stored in that directory as a miniature and its path. They stay there even if you delete these files or if you have previewed them in encrypted HDD or TrueCrypt/VeraCrypt container.

This is an issue that's existed for at least eight years and concerns have been raised about it in the past, but Apple has made no changes in macOS to address it. "The fact that behavior is still present in the latest version of macOS, and (though potentially having serious privacy implications), is not widely known by Mac users, warrants additional discussion," writes Wardle.

As Wardle points out, this information is valuable in law enforcement investigations, but most users are not going to be happy to learn that their Mac records file paths and thumbnails of documents from every storage device that's been attached to it.

For a forensics investigation or surveillance implant, this information could prove invaluable. Imagine having a historic record of the USB devices, files on the devices, and even thumbnails of the files...all stored persistently in an unencrypted database, long after the USB devices have been removed (and perhaps destroyed). For users, the question is: "Do you really want your Mac recording the file paths and 'previews' thumbnails of the files on any/all USB sticks that you've ever inserted into your Mac?" Me thinks not...

It's worth noting that if the main drive on the Mac is encrypted, the Quick Look cache that's created is too. Wardle says that data "may be safe" on a machine that's powered off, but on a Mac that's running, even if encrypted containers are unmounted, the caching feature can reveal their contents.

"In other words, the increased security encrypted containers were thought to provide, may be completely undermined by QuickLook," writes Wardle.

Wardle recommends that users concerned about unencrypted data storage clear the Quick Look cache manually whenever a container is unmounted, with instructions for this available on Wardle's website. It's also worth checking out Wardle's site for full details on the Quick Look bug.

Article Link: macOS 'Quick Look' Bug Can Leak Encrypted Data Through Thumbnail Caches

 

[magicschoolbus]

This is an issue that's existed for at least eight years and concerns have been raised about it in the past, but Apple has made no changes in macOS to address it. "The fact that behavior is still present in the latest version of macOS, and (though potentially having serious privacy implications), is not widely known by Mac users, warrants additional discussion," writes Wardle.

Apple does not care about the Mac. The hardware and this proves it. You guys should seriously consider naming this site iosrumors.com (that's not a shot at you either.. Apple is all about iOS)

 

[syntax]

Just to be clear: the current implementation of FileVault encrypts the entire hard drive, effectively neutralizing this vulnerability, correct?

 

[AL1630]

Hmm. It seems like these flaws are becoming more common lately. Not sure if that's just me paying more attention or if the amount of flaws is actually increasing.

 

[Dave-Z]

Just to be clear: the current implementation of FileVault encrypts the entire hard drive, effectively neutralizing this vulnerability, correct?

It's encrypted at rest. So if the computer is booted someone could walk up and access the files. Even the lock screen is not enough for a determined person. If the computer is powered off it should be fine with a sufficiently strong password.

 

[iapplelove]

Apple does not care about the Mac. The hardware and this proves it. You guys should seriously consider naming this site iosrumors.com (that's not a shot at you either.. Apple is all about iOS)

Apple is all about where the revenue comes from. You would too. We all would.

iPhone is their main source of revenue.

Still though it’s a damn shame they can’t at least keep a healthy Mac lineup going.

 

[InuNacho]

I’ve known about this for years. I accidently locked a word file and was able to “rescue” it by hitting the space bar.
Great security.

 

[pat500000]

Think hopeless. New motto.

 

[oldmacs]

Apple is all about where the revenue comes from. You would too. We all would.

I would. It is possible to care about both.

 

[jchap]

Without wanting to endorse a product that provides a "solution," CleanMyMac users might be interested to know that they can manually clean the QuickLook cache using the "System Junk" clean function of the app.

 

[wlossw]

Onyx also provides this functionality.

 

[supercoolmanchu]

So... use Automator to create a script to clear the cache, then add to startup items?

 

[funman895]

How do we know that this isn't a bug and Apple just uses a Star Wars cypher for their encryption?

 

[luvbug]

It's a one line command (in terminal) to clear the cache. You need to be an "admin" user, but you don't need to be root:

qlmanage -r cache

Of course, someone here will figure out a reason to whine about having to do this.

 

[jchap]

It's a one line command (in terminal) to clear the cache. You need to be an "admin" user, but you don't need to be root:

qlmanage -r cache

Great tip—very good to know! Thank you for sharing this.

 

[luvbug]

Great tip—very good to know! Thank you for sharing this.

Your welcome, although this info came from the blog post that's linked in the MR article above. I knew most people would rather whine, criticize, and/or blame Tim Cook, than read the blog, so I posted the meaningful bit.

 

[citysnaps]

Apple does not care about the Mac. The hardware and this proves it. You guys should seriously consider naming this site iosrumors.com (that's not a shot at you either.. Apple is all about iOS)

Yes, of course. That's why you never see macOS updates from Apple. Right?

 

[Acidsplat]

It's a one line command (in terminal) to clear the cache. You need to be an "admin" user, but you don't need to be root:

qlmanage -r cache

Of course, someone here will figure out a reason to whine about having to do this.

You shouldn't have to do this because of a bug in the software left in from literally years ago.

 

[tjktony]

So... use Automator to create a script to clear the cache, then add to startup items?

Any idea how to do this?

 

[luvbug]

You shouldn't have to do this because of a bug in the software left in from literally years ago.

So, you get the prize for first whiner! I guess assigning blame is more important to you than addressing the problem in the first person using readily available information.

 

[ignatius345]

Your welcome, although this info came from the blog post that's linked in the MR article above. I knew most people would rather whine, criticize, and/or blame Tim Cook, than read the blog, so I posted the meaningful bit.

I personally won't bother clearing my QL caches because the convenience of the preview outweighs some very, very implausible attack on my low-value data -- but this does seem like a very sensible and quick fix for those with greater security needs than myself.

For anyone who uses Alfred, by the way, you can enter terminal commands right into the search window by starting with a ">" character and then entering the terminal command you want to run. It'll call up a Terminal window and enter the string for you right away. Makes this command even faster to run, until such time as the bug properly fixed.

 

[Icy1007]

Seems like a pretty minor issue in my opinion.

 

[Baymowe335]

Apple does not care about the Mac. The hardware and this proves it. You guys should seriously consider naming this site iosrumors.com (that's not a shot at you either.. Apple is all about iOS)

This is simply not true. Software has bugs and Apple will fix them, better than others. A tiny software bug that will be fixed isn’t a referendum on the state of the Mac every single time.

Apple doesn’t update hardware based on what you think is appropriate. They have all the data and facts to back up their strategy, which is working.

Mac revenue is still holding strong, up slightly y/y. Mac is <10% of their revenue but still a large ~$25B/yr business. They do care, but Apple understands what they’re doing. The vocal minority isn’t reality. If it were a major emergency, you’d see them update the various Mac lines. The reality is, it’s just not an issue.

 

[luvbug]

This is simply not true. Software has bugs and Apple will fix them, better than others. A tiny software bug that will be fixed isn’t a referendum on the state of the Mac every single time.

Apple doesn’t update hardware based on what you think is appropriate. They have all the data and facts to back up their strategy, which is working.

Mac revenue is still holding strong, up slightly y/y. Mac is <10% of their revenue but still a large ~$25B/yr business. They do care, but Apple understands what they’re doing. The vocal minority isn’t reality. If it were a major emergency, you’d see them update the various Mac lines. The reality is, it’s just not an issue.

Thank you! That was refreshing!

 

[Acidsplat]

So, you get the prize for first whiner! I guess assigning blame is more important to you than addressing the problem in the first person using readily available information.

Ordinary people wouldn’t know to input a terminal command, or even know that Quick Look is leaking their data.

The bug lies with Apple’s code. How is this the fault of the consumer? The consumer is certainly not the party to blame in this situation.