Slashdot Mirror
Malicious Video Link Can Cause Any iOS Device To Freeze (9to5mac.com)
A new bug in iOS has surfaced that will cause any iOS device to freeze when trying to view a certain .mp4 video in Safari. YouTube channel EverythingApplePro explains the bug in a video titled "This Video Will CRASH ANY iPhone!" 9to5Mac reports: As you'll see in the video below from EverythingApplePro, viewing a certain video in Safari will cause iOS to essentially overload and gradually become unusable. We won't link the infectious video here for obvious reasons, but you can take our word for it when we say that it really does render your device unusable. It's not apparently clear as to why this happens. The likely reason is that it's simply a corrupted video that's some sort of memory leak and when played, iOS isn't sure how to properly handle it, but there's like more to it than that. Because of the nature of the flaw, it isn't specific to a certain iOS build. As you can see in the video below, playing the video on an iPhone running as far back as iOS 5 will cause the device to freeze and become unusable. Interestingly, with iOS 10.2 beta 3, if you let an iPhone affected by the bug sit there for long enough, it will power off and indefinitely display the spinning wheel that you normally see during the shutdown process. If someone sends you the malicious link and you fall for it, this is luckily a pretty easy problem to fix. All you have to do is hard reboot your device. For any iPhone but the iPhone 7, this can be done by long-pressing the power and Home buttons at the same time. The iPhone 7, of course, uses a new non-mechanical Home button. In order to reboot an iPhone 7, you must long-press the power button and volume down button at the same time.
But no, instead let's speculate about how a malicious hacker wearing a hoodie starting at green HTML code crafted this devastating HACK!
or just load IOS 10... my iPhone 5S freezes all the time now.
The new rick rolled
Great, isn't it?
So, iOS uses GStreamer?
this is the link to the video that will crash apple products. Share with all your iFiends. ;)
Anons need not reply. Questions end with a question mark.
Sure, all you have to do is test absolutely every combination of HTML, CSS, JavaScript, SVG, and MP4 streaming configuration you could ever possibly conceive of.
Keep in mind, the MP4 spec is... extensive:
https://en.wikipedia.org/wiki/...
My Other Computer Is A Data General Nova III.
Yay.
my iPhone 5S freezes all the time now.
put it in a glass with gin and tonic, shaken not stirred.
it's simply a corrupted video that's some sort of memory leak
Maybe is the browser/player/library to have a memory leak triggered and exploited by means of a specially crafted video file!
ah!
Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
To freeze or to burn into flames ?
"We won't link the infectious video here for obvious reasons", yeah, no. "I wont link to this" is the battlecry of liars on the internet, and thus I can safely assume that this article was also penned by a liar. Even if it's true I have become wary of all forms of news following this election and the Gamergate debacle showing just how many news writers are filthy fucking liars.
If all the facts are not presented, I will consider it "fake news". A major fact was not presented, thus I dub this fake news.
This doesn't do anything to my iPhone. Did Apple already fix it?
Maybe not in video, but I worked at an image processing place where we deliberately created a file called "bastard.tif". The purpose of this file was to exploit every aspect of TIFF we could find, and for those familiar with the standard you'll know that's a lot. We used non-standard pixel ratios, we switched encoding mechanisms multiple times through the file...we did everything we could to make a standards-valid TIFF that would crash everything.
Wasn't malicious, we were a commercial data processing shop and image creation/conversion was our thing. We could crash Photoshop (non-square pixels - this is early-to-mid-nineties, no idea if it still crashes it), we could bring down things like Kofax Libraries which at the time were fairly advanced pro image coding libraries. We could crash most Unix utilities for working with images...you get the idea. We definitely were thinking about it, and we were actually doing it. The idea was to know what we could and couldn't do whilst coding our image processing software - we didn't want to create a final image that, whilst technically valid, couldn't actually be used anywhere.
They were just lazy. We had the exact same discussions in FFmpeg, and guess what? In almost all cases you can do it efficiently, usually by requiring a few extra bytes of padding so you don't need to do a bounds check at every bit. The remaining checks cost less than 1%.
Of course that then leads to users complaining that they have to pad their buffers, but such is life!
There was some discussion about having a mode that doesn't require padding, and in some cases even that is reasonable, but in quite a few other cases it would mean you can't really do SIMD properly anymore, since trying to do bounds checks in SIMD code doesn't work very well.
> they do maintain a few projects that are really nice (Clang/LLVM is one of those)
Really? The project where the idea of a library interface is "just dump all code in a .so and export all symbols, including non-namespaced C symbols with generic names that are certain to break some program in the future due to collisions"? You must have a very different idea of "nice" projects than me.
Check yourself, at least 3.8 still exports symbols like ConvertUTF8toUTF16. What could go wrong!
You, Sir, were having too much fun.
working link - http://po.st/tExdYj
Why doesn't this affect all types of computers? Why doesn't it affect Android, Mac OS, Windows, and Linux? Why *just* IOS? That doesn't make sense, there must be something unique about IOS where it doesn't handle video as well as other OS's....
If telephones are outlawed, then only outlaws will have telephones.
Sure, laziness is the problem. FFMPEG released in 2000. QuickTime released in 1991. How well does FFMPEG work on a 16 MHz 68030? Does it work with 8MB RAM?
Well nobody cares to optimize the codecs from back then that much and there might have been cases where accepting the crash risk may have been worth the speedup. Then again, if it was in the early '90s maybe it really wouldn't have been reasonable (not so sure though, a lot of those codecs back then could overrun and crash only in very specific cases which are not so costly to check for).
You'll have to disable a lot of stuff in FFmpeg if you want to run it with 8MB of RAM because with loads of modern and table based codecs the binary is larger than that, but it should work. But yeah, trying to run it on a computer from 1991 would not end well I guess, also since the old codecs are not that optimized.
Apparently you think the only two smart phones in existence are the iPhone and the Galaxy Note 7. Boy are you in for a surprise if you ever crawl out of your basement and actually visit a store that sells cell phones.
To freeze or to still be vulnerable after more than a year?
Of course news about a fake are Fake News.