Some of Our Sources
- Techcrunch
- TutsPlus - Code
- Inspiredology
- Web Designer Depot
- Stylized Web
- CSS Tricks
- Spyre Studios
- Design Modo
- Hashedout
- The Verge
Help Webnuz
Referal links:
August 29, 2013 09:56 pm GMT
A bug in Apple’s CoreText rendering engine in iOS 6 and OS X 10.8 causes any apps that try to render a string of Arabic characters to crash on sight. The string of characters which can trigger the bug which was discovered yesterday and has spread around the hacking and coding community has made its way to Twitter, where even looking at it in your timeline will crash the app. The issue affects apps on iOS 6 and OS X 10.8 but doesnot workon OS X 10.9 Mavericks and iOS 7 beta releases. So whatever bug the characters are triggering, they’ve already been fixed in future releases of the engine. This doesn’t help anyone still on iOS 6 of course. Because it’s a CoreText bug, any apps that access this font framework to render text are affected. This means that any apps that use WebKit like Safari are also affected because WebKit uses CoreText. This is a picture of the string of characters, not replicated here for obvious reasons: If you’d care to experience the bug for yourself, feel free to seek out the tweet in the pic above, I’m not posting a link. For the record: Tweetbot appears to be immune to this, though it also uses the CoreText engine. The characters were discovered and posted on a Russian site yesterday morning. The site claims that Apple has known about the problem for ‘six months’ and has not reacted. There is some evidence of the string appearing on Twitter back in February. The posting includes a request to click the crash report button on any apps affected and report it to Apple. The malicious possibilities are simple: if you send the characters in an SMS, it can initiate a revolving crash of Messages on both OS X and iOS. We confirmed this on both operating systems. You can also deliver the string of text via a web link. You could also change the name of a wireless network to the characters and it will crash any device that scans that network to connect. That being said, this is an extremely specific set of unicode characters, so the possibilities of accidentally coming across it are nil. Unfortunately, once this stuff is out in the wild, it’s all down to who has the knowhow and will to try to use it to annoy or offend. Looks like Facebook has
Original Link: http://feedproxy.google.com/~r/Techcrunch/~3/TwxrvC_FRUE/
Bug In Apple's CoreText Allows Specific String Of Characters To Crash iOS 6, OS X 10.8 Apps
A bug in Apple’s CoreText rendering engine in iOS 6 and OS X 10.8 causes any apps that try to render a string of Arabic characters to crash on sight. The string of characters which can trigger the bug which was discovered yesterday and has spread around the hacking and coding community has made its way to Twitter, where even looking at it in your timeline will crash the app. The issue affects apps on iOS 6 and OS X 10.8 but doesnot workon OS X 10.9 Mavericks and iOS 7 beta releases. So whatever bug the characters are triggering, they’ve already been fixed in future releases of the engine. This doesn’t help anyone still on iOS 6 of course. Because it’s a CoreText bug, any apps that access this font framework to render text are affected. This means that any apps that use WebKit like Safari are also affected because WebKit uses CoreText. This is a picture of the string of characters, not replicated here for obvious reasons: If you’d care to experience the bug for yourself, feel free to seek out the tweet in the pic above, I’m not posting a link. For the record: Tweetbot appears to be immune to this, though it also uses the CoreText engine. The characters were discovered and posted on a Russian site yesterday morning. The site claims that Apple has known about the problem for ‘six months’ and has not reacted. There is some evidence of the string appearing on Twitter back in February. The posting includes a request to click the crash report button on any apps affected and report it to Apple. The malicious possibilities are simple: if you send the characters in an SMS, it can initiate a revolving crash of Messages on both OS X and iOS. We confirmed this on both operating systems. You can also deliver the string of text via a web link. You could also change the name of a wireless network to the characters and it will crash any device that scans that network to connect. That being said, this is an extremely specific set of unicode characters, so the possibilities of accidentally coming across it are nil. Unfortunately, once this stuff is out in the wild, it’s all down to who has the knowhow and will to try to use it to annoy or offend. Looks like Facebook hasOriginal Link: http://feedproxy.google.com/~r/Techcrunch/~3/TwxrvC_FRUE/
Share this article:
Tweet
View Full Article
Techcrunch
TechCrunch is a leading technology blog, dedicated to obsessively profiling startups, reviewing new Internet products, and breaking tech news.More About this Source Visit Techcrunch