It appears to contain a 10MB long UTF-8 mess in both the og:title meta content and in a mailto: link.
I'd guess it's supposed to crash iOS apps by either posting that link if it displays links in a thumbnail element using og:title or otherwise by pasting the huge mailto link contained in the webpage, or perhaps only the e-mail address.
Also the href attribute inside the <link rel="apple-touch-icon"> points to a HTML URL, but that returns a 404...
11.7MB HTML file. It crashes the tab in Chrome 65.0.3324.2 64-bit and locks up Firefox 58.0 64-bit on Windows for me.
Just keep trying many until one hits.
Well I don't think Apple really reads bug reports.
Also, while sandboxing may be designed to prevent this, Messages is probably also designed not to crash on link sharing.
I stumbled over two or three of them in the last couple of years while debugging crash reports sent in by customers.
Seems that text rendering is hard. Maybe fuzzing CoreText would be a worthwhile target to discover vulnerabilities?
It is an i7, 16 GB total (7 GB free), and an SSD.
The whole device shouldn't restart due to malformed text, that's just sloppy. If Microsoft can do it with Windows then Apple can do it on iOS.
view-source:https://web.archive.org/web/20180117063656/https://iabem97.github.io/chaiOS/
Since this page is the top search engine hit for several obvious searches (for example “report apple security vulnerability”), hopefully Mr Masri reported it there.
There have been numerous crash-bugs for the Windows font renderer, and even security exploits using it (especially before windows 10, as earlier than that font rendering was performed in the kernel's space rather than user-land). I wouldn't be surprised to learn of issues (at least of the falling over variety) in common Linux rendering engines and for other OSs too.
0x00007B90: A5CCBACD 8774CCB4 CD81CC8D CC92CD8C .....t..........
0x00007BA0: CD84CC86 CC8FCD8B CD97CD86 CC9BCC8F ................
0x00007BB0: CC8ECC95 CC87CC82 CC94CC9B CC92CC92 ................
0x00007BC0: CC86CD91 CD9BCC86 CC8ECCBD CC84CC8B ................
0x00007BD0: CC91CC88 CD9DCC81 CD81CC81 CC84CCBE ................
0x00007BE0: CC85CCBE CC86CC84 CD82CC86 CD9DCC89 ................
0x00007BF0: CC85CC87 CD8CCD9D CC81CC88 CCBFCC9A ................
0x00007C00: CC82CC86 CD8CCC90 CD9DCC82 CC9ACC80 ................
0x00007C10: CC93CC9B CD84CC89 CD82CD8A CCBECD8B ................
0x00007C20: CDA0CC83 CC8ACC8E CD98CC89 CD97CC80 ................
0x00007C30: CD80CC8A CC8FCDA0 CC80CC80 CD84CD80 ................
0x00007C40: CD8CCD92 CD92CD91 CC90CD98 CC83CC88 ................
0x00007C50: CD84CD9B CCBDCD9B CC84CC8D CDA0CC8C ................
0x00007C60: CC81CD97 CD8BCD86 CD9BCD91 CC8ECCAA ................
0x00007C70: CCA7CD87 CD95CCB1 CCA8CCBC CD9CCCA6 ................
0x00007C80: CCA6CC9D CCAFCCAA CC97CCA0 CC9ECD85 ................
0x00007C90: CCAACCA4 CCB2CCAB CD8ECCAB CD89CD8D ................
0x00007CA0: CCA2CCA8 CCAACC97 CCACCCA3 CCBACD93 ................
0x00007CB0: CC9ECCA9 CD87CCA8 CD96CCAF CCBACCA7 ................
0x00007CC0: CCB1CCBB CCA3CCAE CCABCCA7 CD96CCBA ................
0x00007CD0: CCAFCCA9 CCA0CCB2 CC96CD95 CCAACCAD ................
0x00007CE0: CD9ACCA8 CCB9CCB9 CCB0CCA0 CD88CCBA ................
0x00007CF0: CCA9CD9C CCA3CCA1 CCA0CD8D CC98CCA1 ................
0x00007D00: CCAFCCA1 CC9DCD87 CCA6CC9D CCBACCBA ................
0x00007D10: CCAACD9A CCBACD8D CD88CD93 CCB1CCBC ................
0x00007D20: CCA1CCB1 CCB3CCA4 CD9ACCB0 CCA9CCB2 ................
0x00007D30: CC9DCCAC CCADCCB9 CC9ECD89 CD89CD9C ................
0x00007D40: CCA5CCA8 CC9DCD89 CCBACCA2 CC9CCC9F ................
0x00007D50: CCA5CCBA CD8774CC B4CD81CC 8DCC92CD ......t.........
<!-- hello, this was written by Abraham Masri @cheesecakeufo -->
<!-- I discovered this bug in like 10 minutes -->
https://www.reddit.com/r/iphone/comments/37eaxs/um_can_someo...
also notice the high frequency of 0xCC and 0xCD throughout the code, which are respectively Breakpoint and INT on x86 architecture -- with its 0xCD's always followed by a single byte whose value is less than 0xA0 -- possibly x86 was used as author's development platform...
The lock ups came in waves but was able to close the tab when it was unlocked.
Yeah, go on IRC sometime and you’ll probably find out relatively quick.
Plenty of magic strings that break things on various platforms, hardly just an OS X thing.
I can see that the file alternates between segments of:
- Repetitions of the glyph "t̴́̍̒", which is a lowercase t with a combining tilde overlay, an acute accent, a vertical line above, and a turned comma above
- Random-looking ASCII characters with lots of apostrophes (spelled as ' in the HTML)
- Short sequences of spaces, non-breaking spaces, and zero-width joiners
- Occasional emoji
The "t̴́̍̒"s manage to slow down my terminal and glitch its rendering a bit. Is it that they're unexpectedly tall? But we've had zalgo-text for a while and it hasn't actually crashed devices.
It is news, because there's a _completely passive_ way to crash a device, and crashes nearly always will allow for unauthorized code execution, given enough resources to work on the problem. You could launch a DOS attack on phones this way, and we all know that Cell Phones are how we're warned about emergencies, etc.
For what it's worth, Microsoft Edge, my default browser, had no problems with this page.
A recent version of the OS + support lib added the possibility to reference a font in your app in order to have it downloaded (if necessary) and applied to your views.
IIRC It is restricted to one font delivery system only allowing fonts available on Google fonts. Not because of a power grab, but because fonts are not just graphics but also run a bunch of code.
So unrestricted access would have been a big security hole.
If you want more details, the font team talked about it at length during an Android Developer Backstage podcast episode.
(Or am I wrong? I'm not a professional programmer. I'm just reasoning from common sense.)
If software written in C/C++ crashes and it's not because of a null pointer dereference specifically, then it's realistic to worry about whether it might be because of an exploitable bug (like a buffer overflow, a double-free, etc). One common way for people to try to find exploitable bugs is to script a program to re-run with random input data to figure out which inputs crash it, and then they debug the crashes to see if they're caused by exploitable bugs.
The Erlang programming language, in fact, is built around the idea that as soon as you see data you don't expect, you crash, and an external process will start you back up in a known good state.
Opens imessage again with a message draft so that you can delete the conversation without fetching the linked bug
If program gives up and exits on receipt of unexpected input, that can be perceived as a "crash" by the user but it's not exploitable.
If it's crashing because execution suddenly jumped somewhere it shouldn't be, and the OS killed it, that's more worriesome.
Both of which are WebKit wrappers on iOS.
Achilles: I see the dilemma now. If any record player—say Record Player X—is sufficiently high-fidelity, then when it attempts to play the song "I Cannot Be Played on Record Player X", it will create just those vibrations which cause it to break...So it fails to be Perfect. And yet, the only way to get around that trickery, namely for Record Player X to be of lower fidelity, even more directly ensures that it is not Perfect. It seems that every record player is vulnerable to one or the other of those frailties, and hence all record players are defective. (p77)
When I was 13 I built a program called "BorG" that did a lot of fun stuff and animations (but the effects didn't freeze people for very long) and chatbots - and I charged $3 as shareware. Or $5 if you really liked it. I got about 100 people mailing me envelopes! And I used to grab some of that money when I wanted to buy pizza or food to hang out. Those were the days.
I wonder if anyone here used it? :)
(Langford's story and followup in the links)
Edit: spelling and grammar
That’s what should make people worried a bit.
As to fuzzing: given the complexity of the code and the frequency at which bugs are found, I would expect Apple to fuzz their font rendering code 24/7. Do bugs still surface because there are that many, because the whole rendering engine changes that often, because of compiler bugs that do not show up in instrumented code, or because they don’t fuzz it themselves that well?
I don't think anyone ever intended for text rendering to be a "sufficiently powerful formal system" like second-order logic, number theory, or like Hofstadter says the human brain is. I would hope that, in the absence of bugs, rendering text X on computer system Y would be a plain old computable function.
You'll have more success understanding what it's doing if you decode it from UTF-8 first.
And it's understandable. iOS 11 made my iPhone 7 - the newest one at the time - so unusable I sold it and got a different phone. It went from a good, snappy phone, to a slow mess that took seconds more to open or switch apps, crashed all the time, had UI glitches all over the place, and was so slow it couldn't play locally downloaded audio without stuttering and slowing down. Ew.
Various GUI elements such as title bars, tooltips, and thumbnails of links to Web pages, will try to fit the text they're given in a certain amount of space. If the text is too wide, it'll show some amount of text followed by "...". (I wonder if they're prepared for the text to be too tall.)
I saw Firefox rendering the long sequence of t̴́̍̒ characters in the mailto: link. It was being kerned in a way that made it nearly a solid black smear of pixels.
My guess is that apps are trying to determine how much of this text to show to fit within a certain width (and height?), and this text messes with a kerning algorithm in a way that makes it computationally very difficult to decide. I still don't know what's going on with the rest of the text, and why it can read 20 MB of text without making a final decision.
I always cringe a bit when there's an update because the companies never provide any way to downgrade if you're not happy after.
It's not only Apple responsible, I wish there was some kind of consumer protections.
There should always be a way for a consumer to get a product back to the state is was at the time of purchase.
But on the hand, note the strong pattern of "0xCC" and "0xCD" (could be a coincidence to the x86 Breakpoint/INT code), pacing at a fixed distance throughout the code, as well as the numeric characteristics those parameters (or simply garbage code) to the "0xCC" and "0xCD" exhibit. I just feel that if there are certain numeric relations among those code chunks (for instance, all falling within a certain relatively narrow range, as all the parameters to "0xCD" are less than 0xA0 but above 0x80, a width of 32 units), it probably tells something (assuming it has been crafted in that way, with a meaningful purpose) -- but of course, my chunking method might be wrong and each character point (or instruction) might be longer 2 bytes...
And also note that a 12-MB buffer data devised within 10 minutes always seems to be a bit brute force -- so buffer overrun is quite likely in such case; and then out-of-bound data triggers some unhandlable action (as the app crashes) throughout all the exception handling stack -- in the simplistic scenario, would be a segfault -- but of course, that cheesecakeufo could do a bit more exploration with this buffer overrun -- but I guess that normally takes more than 10 minutes, for normal people....
I stopped working on this bug -- it would be a luxury to play a whole afternoon with this puzzle...do you have any further findings? Well, if I had more time, I probably would change the code a little and open it on an extra device, and see if there are any different effects...
The fact that the embellished t's form these big overlapping blocks makes me think that it's hitting the worst-case behavior of some text layout algorithm.
I don't understand what all the hex digits and apostrophes are for, though.
it looks like the black shades over the character lines are the vestiges left by the non-ascii characters at the beginning of the code.
the displayed part is not just ascii hex and apostrophes characters, there are also punctuation characters there...My guess is that if they are displayed, then that means the system has already successfully handled them and their triggered actions have been contained in defined system behaviors...
hence I can only make guesses...if I had a spare one, I would try to modify the content of code and see what would happen (do things such as reducing the code size -- most of the code are repetitive -- and see what would happen if we only retain the core part; or only retain the first half of the entire code -- those 0xCC and 0xCD part; or only retain the second half, those displayable ascii chars)...trim the code down to smaller units and test on them individually (in the same sense as modular testing).