#Malwarebytes 10.9 mac

And youвЂ™ve verified that youвЂ™re running macOS 10.13.1 build 17B1003 (which you can do by choosing About This Mac from the Apple menu and clicking the version number in the window that opens). YouвЂ™ve installed Security Update 2017-001. I know you want to go home, but unfortunately, thereвЂ™s still a problem. Crisis averted, right? Bob, youвЂ™re really going to have to stop jumping out of your chair every couple paragraphs. Of course, Security Update 2017-001 exists for 10.13.1 as well, and will be automatically re-applied sometime after the 10.13.1 update. The process of installing the 10.13.1 undoes the fix that was applied by Security Update 2017-001, making the machine vulnerable to the вЂњiamrootвЂќ bug again. If you install Security Update 2017-001 on 10.13.0, then update to 10.13.1, the bug will re-emerge. Remember how we said that Security Update 2017-001 could be applied to both macOS 10.13.0 and 10.13.1? What happens if you install the update on 10.13.0, then update later to 10.13.1? Turns out, itвЂ™s bad. Take note of the fact that this second update increments the build number of macOS to 17B1003. YouвЂ™ve got another problem to deal with now. YouвЂ™re going to have to go back to your desk in IT. So if you didnвЂ™t do it manually, your confusion wasnвЂ™t going to keep you from getting the update. Fortunately, again, the update was automatic.

Thus, people who had already installed Security Update 2017-001 found themselves wondering why they had to install it again. Yup, thatвЂ™s a second Security Update 2017-001, not Security Update 2017-002.

#Malwarebytes 10.9 how to

So if you relied on being able to use file sharing to move files from one Mac to another, this update wreaked havoc with your workflow.ДЄpple quickly released a technical note about the file sharing problem, and how to fix it, and then re-issued Security Update 2017-001.

Specifically, it made file sharing stop working. We can all go home now! Wait, whatвЂ™s that you say, Bob? SomethingвЂ™s wrong with file sharing?ДЄpparently, AppleвЂ™s first attempt at fixing the bug had a problem. ItвЂ™s a quick install and doesnвЂ™t require a reboot. In other words, if you donвЂ™t install it right away, it will be installed automatically after a fairly short interval. Because of the severity of the problem, this update was pushed out automatically. Security Update 2017-001-the one for High Sierra-was released to fix the вЂњiamrootвЂќ bug, and it was released for both macOS 10.13.0 and 10.13.1. Yes, you read that rightвЂ¦AppleвЂ™s using the same name for unrelated security fixes for different versions of the system. It released another in October for macOS 10.11 (Sierra). It released two back in March, for macOS 10.9 and 10.10 (Yosemite and El Capitan). Confusingly, Apple has already released a Security Update 2017-001 several times. In response to this, Apple quickly pushed a fix out the door in the form of Security Update 2017-001. Worse, the vulnerability can be exploited remotely if screen sharing is turned on. To sum up, the vulnerability allows an attacker to gain access to the ultra-powerful root user on any Mac running macOS 10.13.0 or 10.13.1. Last week, we discussed a particularly serious vulnerability, dubbed вЂњiamroot,вЂќ in macOS 10.13 (High Sierra).