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

donmontalvo
Esteemed Contributor II

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

--
https://donmontalvo.com
14 REPLIES 14

donmontalvo
Esteemed Contributor II

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

--
https://donmontalvo.com

Nix4Life
Valued Contributor

@donmontalvo beat me to it. SUS just populated

donmontalvo
Esteemed Contributor II

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

6a0f2aec93194fc4b2ebbf81048f579b

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

12f6b2e4b3f7499196c4476ad4dfedb4

...and 10.11/10.12:

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

686a311b8d694c40b128c128c757faaf

--
https://donmontalvo.com

alexjdale
Valued Contributor III

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

CGundersen
Contributor III

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

donmontalvo
Esteemed Contributor II

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

--
https://donmontalvo.com

donmontalvo
Esteemed Contributor II

@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.

--
https://donmontalvo.com

alexjdale
Valued Contributor III

Yup, we're still on 9.101.0-t1504998263.

CGundersen
Contributor III

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

Workaround

sbirdsley
Contributor

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
Esteemed Contributor II

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

--
https://donmontalvo.com

sbirdsley
Contributor

@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

tcandela
Valued Contributor

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

tcandela
Valued Contributor

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

softwareupdate - l
softwareupdate - ia