Apple was recently embarrased for its Facetime bug in iOS and (far worse) for having a non-functional security bug reporting process.
But now it seems that this Apple has a pattern of failing to make any viable process available for reporting security bugs! Except for a small and exclusive group of researchers, a policy that without a doubt endangers Mac users (and now with two proofs of that in a month).
A reasonable person might conclude incompetence and lack of concern; the former certainly seems to be true, that latter probably not except that where is the process, publicly available process? Weeks to fix a severe problem is unacceptable to the point of disbelief.
To wit, way back on Feb 4 or so, security researcher Linus Henze reported a 0-day as discussed in Claimed 0-Day Exploit for Stealing Every Password in Your Keychain on macOS Mojave and earlier macOS, and summarized below.
As of March 1, Linus Henze has provided (for free) the bug details to Apple, with no response and without reward. How can Apple be taken seriously when it ignores severe vulnerabilities like this?
All the posturing in the world by Tim Cook to the press doesn’t fix this outrageous situation.
Summary of the 0-day
The claim by Linus Henze is:
In this video, I'll show you a 0-day exploit that allows me to extract all your keychain passwords on macOS Mojave (and lower versions). Without root or administrator privileges and without password prompts of course.
This is not the first time. You might remember KeychainStealer from @patrickwardle, released 2017 for macOS High Sierra, which can also steal all your keychain passwords. While the vulnerability he used is already patched, the one I found still works, even in macOS Mojave. I won't release this. The reason is simple: Apple still has no bug bounty program (for macOS), so blame them.
Apple talks a good PR story (congratulations to Tim Cook for his persuasion), but the bottom line is that a mind-blowing run of serious security flaws in macOS is prima facie evidence of software development incompetence chained to a calendar-based ship-it-testing-be-damned schedule.
What MPG wants to know is whether Apple acknowledges or denies this bug and (particularly important) if Apple is paying bug bounties for such stuff, so that the Bad Guys don’t get hold of it. Tim? Where’s the beef, is it a nothingburger or what?