Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The link provided shows no download for the update, let alone anything in the App store. So it can not be said that it has been "released". Released is exactly that; released to be downloaded. Announced is a different thing. It has been announced, not released.

BL.
The link provided clearly says released 6th December 2017. Unless I’m reading it wrong
 
Wow, how black and white can the difference be between what some people said on the intel thread and how they now mitigate the iOS based devices..
Would they like to order ice-cream or custard with that big slice of humble pie?
 
The link provided shows no download for the update, let alone anything in the App store. So it can not be said that it has been "released". Released is exactly that; released to be downloaded. Announced is a different thing. It has been announced, not released.

BL.

It is very clear that the mitigation was part of the security patches released last month. It simply wasn't made public as the flaw was still a secret at that point. Some relief as I'm still on El Capitan.

macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan
OS X El Capitan 10.11.6, macOS Sierra 10.12.6, and macOS High Sierra 10.13.1
6 Dec 2017

This document describes the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan.

Kernel

Available for: macOS High Sierra 10.13.1, macOS Sierra 10.12.6, OS X El Capitan 10.11.6

Impact: An application may be able to read kernel memory

Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus Technology GmbH, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology

Entry added January 4, 2018
 
  • Like
Reactions: bwintx
The fixes were indeed backported to Sierra and El Capitain in the Security update.

How do you know this? I am running El Capitan, and would love to get formal confirmation.
[doublepost=1515147235][/doublepost]
It is very clear that the mitigation was part of the security patches released last month. It simply wasn't made public as the flaw was still a secret at that point. Some relief as I'm still on El Capitan.

macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan
OS X El Capitan 10.11.6, macOS Sierra 10.12.6, and macOS High Sierra 10.13.1
6 Dec 2017

This document describes the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan.

Kernel

Available for: macOS High Sierra 10.13.1, macOS Sierra 10.12.6, OS X El Capitan 10.11.6

Impact: An application may be able to read kernel memory

Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus Technology GmbH, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology

Entry added January 4, 2018

That's good news. Why did Apple state that only the latest version of macOS was patched?
 
  • Like
Reactions: RandomDSdevel
That was quick. And yet there were still many crying "Why won't Apple be more open and talk about this!!!!"
not that i am one of those guys who complain but this is a bad example. Companies knew about this issue since very long time. 9th of Jan was coordinated publishing date but because of news leaks **** hit the fan before this date. So not quick in anyway
 
  • Like
Reactions: RandomDSdevel
As of yet no fix has yet been released has been released for macOS 10.12.6 Sierra therefore it can be assumed the same applies to OS X 10.11.6 El Capitan.

Also worth mentioning is there likely to be a fix released for OS X 10.10.5 Yosemite or have Apple completely discontinued support for Yosemite?

Apple need to be clear on when a release has reached its end of life.
[doublepost=1515149591][/doublepost]
It is very clear that the mitigation was part of the security patches released last month. It simply wasn't made public as the flaw was still a secret at that point. Some relief as I'm still on El Capitan.

macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan
OS X El Capitan 10.11.6, macOS Sierra 10.12.6, and macOS High Sierra 10.13.1
6 Dec 2017

This document describes the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan.

Kernel

Available for: macOS High Sierra 10.13.1, macOS Sierra 10.12.6, OS X El Capitan 10.11.6

Impact: An application may be able to read kernel memory

Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus Technology GmbH, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology

Entry added January 4, 2018
Thank you for going some way to clarifying this if it is indeed the relative fix. Apple should be more transparent when issuing fixes for older releases. But what of Yosemite?
 
  • Like
Reactions: RandomDSdevel
My thoughts exactly, I thought that spectre was demonstrated on ARM. All these companies and journalists are contradicting themselves. I imagine there is still a lot of ongoing work and not everything has been made public and clearly not enough coordination amongst the researchers and companies. Seems like everyone is scrambling to get in front of the press.

The BBC seem to have mis-quoted Apple on this, or misunderstood:

Referring to Apples comments..."Meltdown does not affect the Apple Watch, it said, as the bug was an issue with Intel processors which are not contained in that device"

Intel processors aren't contained in iPhones or iPads, but you say they are affected....

It's this scaremongering, non-factual journalism that causes everyone to go bonkers over these things.
 
Far too much FUD going on right now around these issues. I’m sure more factual information will emerge in the coming weeks as patches roll and embargoes formally lift.

In the meantime, let’s keep speculation to a minimum...boom boom! :p
 
  • Like
Reactions: RandomDSdevel
So typical of Apple to be ahead of the game like this. They already fixed most of the bug issue with Mac OS 10.13.2, which was released on December 6th, and will complete patches on 10.13.3. They were a month ahead of the press releases when this Intel "bug" issue became public. Microsoft rushed to release a patch yesterday evening, whereas Apple were comfortably ahead of it all. I have updated to 10.13.2 and have not experienced any performance decreases with my six year old MacBook Pro. Apple has done great with keeping their products number 1. Now the question to be asked is will Apple begin using AMD processor chips rather than Intel because of all of this negative publicity toward Intel.
Actually, Microsoft released first patches on Windows Insider in November and they've been benchmarking the performance since then. Only the official release got out yesterday.
 
These security flaws are gonna cause the biggest OSes version fragmentations in the history of Apple. Mark my words. People's thoughts are going to be something like this: "If I'm screwed up no matter what super new technology I have. Safe computing and to hell with everything else" (Just my thought) :rolleyes:
 
No they are not. Because they can be fixed in software (with a small performance hit). So like before, if you don't update you are vulnerable, if you update you aren't.
 
  • Like
Reactions: RandomDSdevel
Apple added this yesterday to the security notes for iOS 11.2

Kernel

Available for: iPhone 5s and later, iPad Air and later, and iPod touch 6th generation

Impact: An application may be able to read kernel memory

Description: Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis of the data cache.

CVE-2017-5754: Jann Horn of Google Project Zero, Werner Haas and Thomas Prescher of Cyberus Technology GmbH, and Daniel Gruss, Moritz Lipp, Stefan Mangard and Michael Schwarz from Graz University of Technology

Entry added January 4, 2018

https://support.apple.com/en-us/HT208334
 
Last edited:
  • Like
Reactions: RandomDSdevel
Since this is in the OS, and affected other chips i'm sure that would mean Windows systems also affected.

These security flaws are gonna cause the biggest OSes version fragmentations in the history of Apple. Mark my words. People's thoughts are going to be something like this: "If I'm screwed up no matter what super new technology I have. Safe computing and to hell with everything else" (Just my thought) :rolleyes:

20% OS install, 80% updates :D
 
I wonder if this explains why after the latest update for El Cap that my 15-inch MBP (Haswell CPU) was running hotter and noticeably slower, especially when virtualizing? I ultimately wound up doing a carbon clone restore to an OS backup I made before the update was installed.
 
I thought Spectre had no effective mitigation. I wonder what they are adding to Safari to protect against it?
[doublepost=1515159196][/doublepost]
I wonder if this explains why after the latest update for El Cap that my 15-inch MBP (Haswell CPU) was running hotter and noticeably slower, especially when virtualizing? I ultimately wound up doing a carbon clone restore to an OS backup I made before the update was installed.

I understand Virtualization is one of the "workflows" whose performance is most impacted by the mitigation for Meltdown. That said, I run Parallels every day and haven't really noticed it being any slower since the Dec patch.
 
  • Like
Reactions: RandomDSdevel
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.