Home Cyber Security News Mac OS Vulnerability Posed Risk Of Hacking To Apple Users For 11 Years

Mac OS Vulnerability Posed Risk Of Hacking To Apple Users For 11 Years

by Abeerah Hashim

When we say “apple”, perhaps we think of all those techy gadgets (iPhones and Mac) even before the real apple fruit. Isn’t that right? Apple has thrived to establish itself as the most secure and private OS of all time. Ironically, we never knew this ‘safest’ system has in fact kept its users prone to hacking for 11 years. The latest identified Mac OS vulnerability shows how third-party apps could have tricked into Apple software by bypassing the Apple code-signing process.

Mac OS Vulnerability Allowed Malware To Bypass Apple Signature

On Tuesday, Josh Pitts, a security researcher and staff engineer at Okta reported in detail about a Mac OS vulnerability. Precisely, he addressed the issues revolving around Apple’s third-party code-signing checks. He pointed out how third-party developer’s interpretation of code signing API bypassed Apple’s signature and misinterpreted unsigned malicious codes as being signed by Apple.

Because of this misinterpretation, hackers had a wide opportunity to dump malicious codes that any third-party developers may use by misinterpreting them as being Apple verified. In this way, malware could easily access Apple customers devices. Precisely, this code-signing bypass was mainly affecting Mac OS and some older versions of OSX.

Patrick Wardle, CRO DigitaSecurity and Objective-See tools developer, does not consider this problem as a ‘vulnerability’. According to him, bypassing signatures is always easy for hackers.

“If a hacker wants to bypass your tool and targets it directly, they will win,” says Wardle. “To be clear, this is not a vulnerability or bug in Apple’s code. Basically, just unclear/confusing documentation that led to people using their API incorrectly.”

Tricking Code-Signing Was ‘Easy’ And ‘Trivial’

Apple requires third-party developers to use code-signing API. However, the process by which Mac OS security tools checked for digital signature was trivial to bypass. Anyone knowing this ease of evading Apple signature could then throw in malware as a signed app. As Mac OS used the same process since 2007, the risk of malware and hacking was there for the past 11 years.

Josh Pitts has explained well how anyone could leverage flaw to spread malware. He himself demonstrated the flaw where his file ‘ncat.frankenstein’ appeared digitally signed, even though it wasn’t Apple verified. According to him, the vulnerability works in certain conditions. If a hacker knew about them, he could bypass codesign.

“On macOS/iOS, code signing focuses on the Mach-O binary and application bundles to ensure only trusted code is executed in memory,’ says Josh Pitts. “This vulnerability exists in the difference between how the Mach-O loader loads signed code vs how improperly used Code Signing APIs check signed code and is exploited via a malformed Universal/Fat Binary.”

Josh Pitts first discovered the problem in early 2018, when he reported the details to Apple. However, Apple, at that time, didn’t consider this as a security issue. But, as he continued communicating with Apple over the matter, things changed. He has shared a detailed timeline showing how his efforts started on February 22, 2018, however it took a while to disclose this matter to the public on June 12, 2018.

Let us know your thoughts in the comments below.

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