Home Cyber Security News Apple Silently Enhanced iMessage Security With BlastDoor Sandbox in iOS 14

Apple Silently Enhanced iMessage Security With BlastDoor Sandbox in iOS 14

by Abeerah Hashim
BlastDoor sandbox iMessage

A security researcher from Google’s Project Zero security team, Samuel Groß, has shared a detailed blog post about iOS 14.

As revealed, Apple has introduced one more sandbox with the latest iOS. Identified as BlastDoor, this sandbox within iOS 14 protects users from incoming threats targeting the iMessage client. It processes every message, thus preventing any malicious content with the messages from reaching the operating system to cause damages.

Describing BlastDoor, the post reads,

One of the major changes in iOS 14 is the introduction of a new, tightly sandboxed “BlastDoor” service which is now responsible for almost all parsing of untrusted data in iMessages (for example, NSKeyedArchiver payloads). Furthermore, this service is written in Swift, a (mostly) memory safe language which makes it significantly harder to introduce classic memory corruption vulnerabilities into the code base.

This diagram illustrates the processing flow of iMessage in iOS14.

BlastDoor iMessage in iOS 14

Source: Project Zero

Apple already includes multiple sandbox services within the iOS. That’s how it maintains users’ security.

The new security service caught the researchers’ attention following a Citizenlab report that mentioned a zero-click attack not working against the iOS 14.

Apart from BlastDoor introduction, Apple has also brought two other improvements to iMessage security. These include shared cache resliding that prevents ASLR bypass via cache oracle technique and exponential throttling that limits the number of attempts an attacker requires to exploit a flaw.

Hence, the major structural reengineering that Apple introduced with iOS 14 will potentially protect the users from many security exploits. The same changes have also failed the NSO zero-click vulnerability with the latest iOS.

Let us know your thoughts in the comments.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid