Google is planning to add a new security feature to the Chrome web browser designed to block potential attackers from launching side-channel attacks and tracking a user’s activity by abusing the browser’s HTTP cache.
The new feature will partition Chrome’s HTTP Cache “using top frame origin (and possibly subframe origin) to prevent documents from one origin from knowing whether a resource from a cross-origin was cached.”
This approach will prevent attackers from launching side-channel attacks employing malicious sites they control to detect if another site their target has visited is in their web browser’s cache.
Cache attacks can trigger the following types of information leaks according to the ‘Partition the HTTP Cache’ security feature’s Chrome Platform Status entry:
• Detect if a user has visited a specific site: If the cached resource is specific to a particular site or to a particular cohort of sites, an adversary can detect user’s browsing history by checking if the cache has that resource.
• Cross site search attack: There exists some cross site search attack proof of concepts which make use of the fact that some sites (gmail, google search, …) load a specific image when a search result is empty. By opening a tab and performing a search and then checking for that image in the cache, an adversary can detect if an arbitrary string is in your search results.
In addition, the browser’s cache can also be used as a user fingerprinting method by storing cross-site super-cookies which require the targets to completely clear the browser’s cache to delete them.
Attacks abusing Chrome’s HTTP cache
This example HTTP cache-based attack shows how a bad actor can easily collect sensitive information about a Chrome user by abusing Google vulnerable endpoints. As explained by the researcher who documented this specific attack, “the impact varies from retrieving the private book collections to obtaining all the user’s contacts char by char.”
Vulnerable sites that could be used in these attacks range from Google’s Mail and Search to Google Books and YouTube. Users who would visit a maliciously designed website after browsing these Google websites could have their sensitive information exposed.
The types of data attackers could get their hands on in the event of a successful side-channel cache attack are a user’s:
• search history,
• videos watched
• the exact URLs visited
• time frames of the activities
• private book collection
• books read / purchased / bookmarked / favorite / etc.
• private emails
• tokens / credit card numbers / phone numbers / etc.
• frequency of mailing
• people the user’s email with
• contacts (including email addresses, names, phone numbers)
• private notes
• bookmarked websites
• and more
Changes needed to mitigate cache attacks
According to the feature’s design spec the “solution is to partition the disk cache by the origin of the top-frame of the page (e.g., what shows up in the omnibox) or by the combination of top-frame and sub-frame origins. This way resources loaded for one origin can’t be read by another and both problems are resolved.”
The current option to be used for cache isolation and cache attacks mitigation are:
• (top frame origin, request URL) as the double key
• (frame origin, request URL) as the double key
• (top frame origin + frame origin, request URL) as a triple key
The Chrome developers have currently proposed the “top-frame-origin for sub-resource requests and document initiator for shared/service worker requests” as the mitigation solution of choice, but they’re still collecting more data to make the final decision.
“Chrome hasn’t addressed this problem in the past due to concerns that the cache hit rate would be dramatically reduced, causing large increases in network usage and longer page loads,” says Google Software Engineer Shivani Sharma on the feature’s HTTP Cache Threat Model document.
“Recent experiments in canary and dev channels show that contrary to our earlier thinking, the losses would be acceptable.”
The end goal of the planned partitioned HTTP cache feature is to “prevent documents from one origin from knowing if a resource from a cross-origin document load was cached or not,” adds Sharma.
Out of all major browsers, Safari is the only one which has already implemented a version of this feature more than six years ago, while Mozilla already has shown that it publicly supports the new security enhancement and Microsoft hasn’t yet given any public signals of any plans to implement cache partitioning in their Edge browser.
Related Articles:
Enterprise Software May Transmit Data Without Your Knowledge
Google Chrome to Limit Referer Header Size to Block Attacks
Chrome 76 Released With Blocked Flash, Incognito Detection Fix
New York Passes Law to Update Data Breach Notification Requirements
Get 97% off The A to Z Cyber Security & IT Certification Training Bundle Deal
Bleeping Computer® is a community of individuals of all ages who are here to learn new information, to help each other, and to help their fellow peers. With that in mind, we ask that all members please follow these simple rules in order to create an atmosphere where everyone feels comfortable.
The rules are as follows:
- All information and instructions given within these forums is to be used at your own risk. By following or using any of this information you give up the right to hold BleepingComputer.com liable for any damages.
- All the forums are categorized by topics. Please post your questions or messages in the appropriate forum.
- Answers to many of the questions you may have can be found in the Tutorials Section, Glossary, or from other posts on the message boards. Please use the search functions, at the top right of each page, to find your answers. If you are still having problems, feel free to post your question.
- All help must be provided in the forums or on our Discord Server. We do not allow support to be provided or requested via personal message, email, or remote desktop control programs (Logmein, TeamViewer, etc).
- If a topic is posted in a forum that is not appropriate for the question, the staff has the right to move that topic to another better suited forum.
- The posting of any copyrighted material on our web site is strictly prohibited.
- Posting links in order to generate affiliate commissions is not permitted at BleepingComputer.com. Any posts that are deemed to be posted in order to generate affiliate commissions, regardless of the product being promoted, will be deleted. If a user continues to create affiliate SPAM posts, they will be banned.
- Posting links to non-Bleeping Computer malware removal guides is NOT permitted with the exception of security vendors who sometimes release specialized tools and instructional documentation. This is because it is impractical for BleepingComputer to monitor and review all such guides for accuracy, no matter how accurate those guides may, in fact, be.
- There will be no use of profanity on our message boards. This will not be tolerated and can lead to immediate suspension.
- When posting, please use proper grammar. Refrain from ‘text-message’ style substitutions of words like ‘u’ for ‘you’, and ‘ur’ for ‘your’. This is a multi-national forum, and some of our non-english speaking members must use translation software which is confused by abbreviations. Most of our volunteer members are very busy helping as many people as they can, and a post that is hard to read will often be overlooked.
- There will be no racial, ethnic, gender based insults or any other personal discriminations. This will not be tolerated and can lead to immediate suspension.
- There will be no posts meant to offend or hurt any other member, in a manner which is offensive or inflammatory. This includes flaming or instigating arguments.
- Spamming is not permitted; please keep all your posts as constructive as possible.
- Pornography, warez, or any other illegal transactions may NOT be linked in any shape or form.
- If you have questions regarding homework, we will only help you with general concepts. If you are looking for a complete solution or answer, we will most likely just delete your post.
- No subject matter will be allowed whose purpose is to defeat existing copyright or security measures. If a user persists and/or the activity is obviously illegal the staff reserves the right to remove such content and/or ban the user. This would also mean encouraging the use or continued use of pirated software is not permitted, and subject to the same consequences.
- If you are receiving assistance in the Virus Removal forum, you are not allowed to request assistance for the same computer at another malware removal forum. This is to prevent conflicting advice from causing issues with your computer or making it unbootable.
- This forum has the right to request alteration or deletion of any offensive post. If this is not done in a prompt manner, the Staff will delete the material themselves.
- Posts may be deleted for any reasons the forum administrators deem reasonable.
- Pictures may be posted as long as they are not explicit, offensive, or copyrighted.
- Advertisements, of any sort, are not permitted. This includes member names and links to commercial sites in Signatures, or in posts. You also may not solicit sales for Newegg through the use of promotion or coupon codes. If you would like to advertise on our site, contact us here.
- In order to reduce spam on the site, you will not be able to add a signature to your account until you reach 25 posts. Signatures are limited to 5 lines or 2000 characters; whichever comes first. If your signature is larger than the allotted size given or deemed unacceptable, you will be requested to adjust your signature. Failure to comply will result in the removal of your signature.
- Only one image per signature. Images in signatures must also be no larger than 500 pixels wide X 90 pixels high. If you have more than one image you will be requested to remove one. If this is not done in a timely manner the staff has the right to modify your signature to abide by these rules.
- Any links in signatures or profiles cannot be commercial in nature or they will be removed by BleepingComputer. You may not put links in your signature soliciting donations unless you are in certain member groups. Those member groups that are allowed will be expressly notified. If you have a personal website or off-site help resource, that is more than fine, but you can not sell products or services through your signature. Multiple links to the same site, unless for a very specific reason, are not permitted in a signature and will be removed.
- Avatars must be in good taste. This means no vulgar or violent images, pornography, or profanity. Avatars that are found to be inappropriate will be removed at the discretion of the staff.
- Linking to hate, anti-Semitic, racist, pornography, warez, or other illegal sites is not permitted.
- Links in your signature must be unobtrusive and can not use formatting so that attention is brought to them.
- Member’s display names can not be email addresses. This rule is in place to protect you from spam bots who will pick up your email address and spam you.
- Members may have only one account on this forum. There is no need to have more than one.
- Any impersonation of a user from these forums, in any mode of communication, is strictly prohibited and will result in a banning.
- Linked and locked topics are pruned regularly to reduce page clutter. If you have a question about where your topic went, please PM a Moderator or Administrator before starting a new topic asking where it went, or posting a duplicate of the original topic. We will be happy to provide you with a link to the new location, or a reason why it was locked and/or removed.
Violation of any of these rules can lead to a banning of the user from our Web Site and a deletion of their account. The consequences will be determined by the Staff on a case by case basis.
When posting you agree that the administrators and the moderators of this forum have the right to modify, delete, edit or close any topic, signature, account, or profile data at any time that they see fit. If you have any questions concerning this, please do not start a new thread, but rather private message to an administrator or moderator.