Impact: An application may be able to gain elevated privilegesĭescription: A race condition was addressed with additional validation.ĬVE-2017-13905: Samuel Groß added October 18, 2018Īvailable for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS High Sierra 10.13.1 Impact: Processing a maliciously crafted Apache configuration directive may result in the disclosure of process memoryĭescription: Multiple issues were addressed by updating to version 2.4.28.
This was addressed with improved state management.Īvailable for: OS X El Capitan 10.11.6, macOS Sierra 10.12.6, macOS High Sierra 10.13.1 Is this a known Mac High Sierra bug or expected/accepted behavior? As it seems to transcend browsers I feel it has to be at the OS level.Impact: APFS encryption keys may not be securely deleted after hibernatingĭescription: A logic issue existed in APFS when deleting keys during hibernation. I came across this because it seems to effect date/time pickers on several websites I've come across.
I have recreated similar symptoms in Firefox which are leading me to think this is an OS level anomaly. Short of a full system reset, the page (tab actually) seems to be stuck on UTC. Note, by the offset, the time is, in fact, accurate, but the darn part is, if you switch your time zone BACK, it still sticks to GMT+000 (UTC). Now in the Chrome console (before OR after refresh) enter: new Date() // result will be something like ue 23:23:29 GMT+0000 (UTC) Now open date & time preference and switch your time zone (anywhere different). In Chrome open the javascript console and enter: new Date() // result will be something like Tue 16:20:14 GMT-0700 (MST) While trying to figure out exactly how to express my question, perhaps it is just easier to demonstrate: Since time and time zones can be a little confusing, to begin with, I have stumbled onto something truly bizarre in regards to JavaScript and macOS High Sierra time.
0 kommentar(er)
