Disclosure to Apple - Apple notified 12-11-12. I often wonder why disclosures of these types of exploits is now, "same day" instead of "Let vendor know you will be reporting this to public in a week." I wonder if it is out of concern they will be pressured to keep quiet? There is a good practical reason for not providing advance disclosure at major conference, particularly if you're subject to some kind of NDA, becau…
IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
11–20 of 54 posts
Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#12The title is incorrect. "... this one crashes the Mac, and it makes [Windows] Server 2012 restart."
Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#13Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#14Disclosure to Apple - Apple notified 12-11-12. I often wonder why disclosures of these types of exploits is now, "same day" instead of "Let vendor know you will be reporting this to public in a week." I wonder if it is out of concern they will be pressured to keep quiet? There is a good practical reason for not providing advance disclosure at major conference, particularly if you're subject to some kind of NDA, becau…
"The new version of the attack is powerful enough that I decided to formally notify Apple. I don't expect them to care much--Microsoft certainly didn't think this was important to them, and Windows is much more vulnerable."
Its also worth noting that while this vuln has a high availability impact it is also requires very specific network access, ie you can't run this from your cable modem and kill a random box on the internet.
Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#15Disclosure to Apple - Apple notified 12-11-12. I often wonder why disclosures of these types of exploits is now, "same day" instead of "Let vendor know you will be reporting this to public in a week." I wonder if it is out of concern they will be pressured to keep quiet? There is a good practical reason for not providing advance disclosure at major conference, particularly if you're subject to some kind of NDA, becau…
Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#16Disclosure to Apple - Apple notified 12-11-12. I often wonder why disclosures of these types of exploits is now, "same day" instead of "Let vendor know you will be reporting this to public in a week." I wonder if it is out of concern they will be pressured to keep quiet? There is a good practical reason for not providing advance disclosure at major conference, particularly if you're subject to some kind of NDA, becau…
I take it 12/11/12 is a December date, not the November one that it is by convention here... I missed that and assumed a month had been given, as screen grabs show November dates.
o First posted: 7:30 am 11-20-12 by Sam Bowne
o Page reorganized with Contents section 11-30-12 10:36 am
o New videos 4 and 5 added 12-5-12
o BayThreat Videos added 12-8-12 11:19 pm
o Attacks on the Mac OS X with simulated routers added 7:45 pm, 12-10-12.
o Apple notified 12-11-12Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#17Reminds me of the '90s when WinNuke and Smurf attacks ran wild. Remember one attack that caused our Linux boxes to panic, but I can't remember what it was called. It's not surprising that we're seeing stuff like this in v6. IPv4 has had the bugs hammered out from years of attacks, v6 not so much.
http://www.physnet.uni-hamburg.de/physnet/security/vulnerabi...
Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#18Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#19It would be interesting to know if iOS is affected as well.
Re: IPv6 Attack Kills Mac OS X and makes Windows Server 2012 restart in Seconds
#20In the video, he tested OS X, Windows XP, and Server 2012. OS X beachballed, XP went to 100% CPU, and Server 2012 panicked and rebooted. All three failed; this isn't just an Apple issue. Was Microsoft notified as well?