I've never done any fuzzing personally, but wouldn't this be discoverable internally during testing? I would think that they would attempt sending all possible characters, especially because they've had issues with this in the past.
I would hope that after all the character-crashing-everything bugs that have hit iOS there is a team dedicated to replacing the text rendering code with something more fault tolerant.
Major new iOS bug can crash iPhones and disable access to apps and iMessages
51–60 of 122 posts
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#52Wow its just unicode character in a language spoken by just 75Million people https://en.wikipedia.org/wiki/Telugu_language
However, there are similar test cases for Bengali, and ZWNJ does have an effect on some Bengali vowels, so it's definitely a real world character in that case.
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#53Earlier quoted context omitted.
Fuzzing finds bugs, using a safe language precludes them.
No it doesn't. At best it precludes a certain class of bugs (which may be very significant, but it's not a silver bullet)
function ThisWillNeverCrash() {
console.log('hello');
stack.push('it');
setTimeout(ThisWillNeverCrash, 0);
}setTimeout(ThisWillNeverCrash, 0);
// my point in posting this was to demonstrate a bug ... that array will eventually run out of memory and this loops infinitely but not using a standard language loop construct... but I see someone didn’t think that was relevant
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#54This isn't the first time a weird sequence of Unicode characters has caused the text renderer to crash and create problems for iOS users. This is why we shouldn't be writing new code in C.
[1] - https://github.com/kdeldycke/awesome-falsehood
[2] - https://www.joelonsoftware.com/2003/10/08/the-absolute-minim...
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#55This isn't the first time a weird sequence of Unicode characters has caused the text renderer to crash and create problems for iOS users. This is why we shouldn't be writing new code in C.
Also, non-C languages frequently implement lots of library features on top of C because it would be a ton of work not to (and slower), which means any language could be at risk.
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#56This isn't the first time a weird sequence of Unicode characters has caused the text renderer to crash and create problems for iOS users. This is why we shouldn't be writing new code in C.
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#57Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#58Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#59What Apple, and Microsoft before them, are discovering is the tools and processes we use to create software simply doesn't scale. We're simply reaching the limits of what these giant software teams are able to produce and keep running. We can discuss solutions, but currently not everybody even agrees we have a problem. That's the first step we need to take.
I disagree that this is the product of scale. Looking at some of the bugs coming out of Apple lately and how they respond to them (assuming it's really a trend and not just a run of bad luck) it feels like they're slipping into a culture where individual feature teams are making emotional or schedule-based decisions about security without central guidance. A good example is the recent bug on MacOS where a low-privile…
We don't know what kind of and how many errors triggered the failure, nor do we know what the faults causing the errors were.
We certainly don't know what kind of hazard analysis they did and what kind of mitigations they have in place, nor do we know whether they accepted a specific amount of residual risk for e.g. economic or market pressure reasons.
We don't know what kind of QC they do.
Without this information, it's pointless to talk about how things feel or seem. This is a very large engineering organization, working on a very large and complex system. It's not possible to find the root cause (or any cause) of a failure by using guesswork or by reporting to familiar failure cases.
Re: Major new iOS bug can crash iPhones and disable access to apps and iMessages
#60Here's a link to the character if someone wants to test it themselves https://pastebin.com/9Tr8ytTr
I sent this link to my phone and the character is in the meta-title, which then crashed my phone. It works! Now how to fix it...
* Have someone else send you a message
* Click the notification and it'll open their message
* Navigate back and delete the corrupting message
Option 2:
* Sign up for the ios beta program (free) https://beta.apple.com/sp/betaprogram/ and install the latest beta which isn't impacted.