Skip to main content
Question

macOS High Sierra 10.13.2 Supplemental Update (hot off the press)

  • January 8, 2018
  • 14 replies
  • 111 views

donmontalvo
Forum|alt.badge.img+36

macOS High Sierra 10.13.2 Supplemental Update
https://support.apple.com/en-us/HT208397

14 replies

donmontalvo
Forum|alt.badge.img+36
  • Author
  • Hall of Fame
  • January 8, 2018

And patches for Safari for 10.11/10.12.

About the security content of Safari 11.0.2
https://support.apple.com/en-us/HT208403


Forum|alt.badge.img+13
  • Honored Contributor
  • January 8, 2018

@donmontalvo beat me to it. SUS just populated


donmontalvo
Forum|alt.badge.img+36
  • Author
  • Hall of Fame
  • January 8, 2018

Meltdown appears to have been resolved for 10.13 only

About the security content of macOS High Sierra 10.13.2, Security Update 2017-002 Sierra, and Security Update 2017-005 El Capitan https://support.apple.com/en-us/HT208331

Spectre is resolved for 10.13...:

About the security content of macOS High Sierra 10.13.2 Supplemental Update https://support.apple.com/en-us/HT208397

...and 10.11/10.12:

About the security content of Safari 11.0.2 https://support.apple.com/en-us/HT208403


Forum|alt.badge.img+18
  • Contributor
  • January 8, 2018

It looks like this 10.13.2 update breaks recon, like the last supplemental update. At least on 9.101.


Forum|alt.badge.img+14
  • Contributor
  • January 8, 2018

@alexjdale Running 9.101.4-t1507816971 ... applied all updates to a couple of High Sierra machines and not seeing recon issues here.


donmontalvo
Forum|alt.badge.img+36
  • Author
  • Hall of Fame
  • January 8, 2018

Apple deserves to have their icon carved into Mount Rushmore for helping us get to N minus ZERO.


donmontalvo
Forum|alt.badge.img+36
  • Author
  • Hall of Fame
  • January 8, 2018

@alexjdale @CGundersen confirmed we are on JSS 9.101.4-t1507816971 as well, and recon did not break after applying the latest updates to 10.11/12/13. At least not here in our LAB.


Forum|alt.badge.img+18
  • Contributor
  • January 8, 2018

Yup, we're still on 9.101.0-t1504998263.


Forum|alt.badge.img+14
  • Contributor
  • January 9, 2018

@alexjdale It appears you will want to take a look at this thread (if you haven't already):

Workaround


Forum|alt.badge.img+7
  • Contributor
  • January 9, 2018

Any word if there will be updates for 10.11 or 10.12 or is the only way to fully eliminate this vulnerability is to upgrade to 10.13?


donmontalvo
Forum|alt.badge.img+36
  • Author
  • Hall of Fame
  • January 9, 2018

@sbirdsley So far, yes, hence the comment regarding carving the Apple logo onto Mount Rushmore, for finally getting us to N minus ZERO. ;)


Forum|alt.badge.img+7
  • Contributor
  • January 10, 2018

@donmontalvo Thanks for confirming, that is what I was afraid of :( Sounds like time to ramp our our adoption/roll out of 10.13 then


Forum|alt.badge.img+20
  • Contributor
  • January 10, 2018

my 10.13.2 is also having an unknown error when running recon. I am now installing the supplemental update 10.13.2 and let's see if this unknown recon error continues.

jamf version 9.101.0


Forum|alt.badge.img+20
  • Contributor
  • January 10, 2018

After the 10.13.2 supplemental update installed i ran the 'sudo jamf recon' and it successfully completed !!

softwareupdate - l
softwareupdate - ia