The Apple bug isn't really in that class of exploit. It's a simple coding/merge error, and it's actually a regression from previously working code. One of the things that worries me is that this bug would have been caught so easily with basic unit tests.
Test 1: Make connection to server with a valid SSL certificate [PASSED]
Test 2: Make connection to a server with an invalid SSL certificate [FAILED]
Are we meant to think that Apple's build process doesn't use unit testing? Seems unlikely. Or perhaps this component didn't warrant an extensive test suite? I hope not! Not really sure what the explanation is.I mean, I certainly can't claim that all my code is run through extensive tests before every deploy, but then I'm not working on the security tools that underpin an entire operating system.
What would have caught the bug: automatic code indentation or any sort of compile-time warnings about dead code.
Indeed, to err is human. This is why you're a negligent jackass if you don't plan for errors and build multiple systems to prevent and detect them, at least until computers start programming themselves for us.
Vulnerabilities of all kinds exist. We need to find them, learn from them and we need to fix them.
Getting hung up on whether or not they are 'acceptable' is just kind of weird.
Bad stuff happens, incompetence happens, mistakes happen. None of that is 'acceptable', but it happens just the same.
Creating an environment where some kinds of mistakes are 'unacceptable' doesn't eliminate those kinds of mistakes, it just causes people to stop reporting them.
Complaining about their release cycle makes some sense. complaining about the existence of an existing bug is basically just howling at the moon.
if you think you operate and hold yourself to a much higher standard then go ahead and complain all you want. maybe you do... maybe
This is not a reasonable argument. At Pwn2Own each year, how many browsers have vulnerabilities that allow remote code execution? All of them. How many of these vulnerabilities are zero-days? A significant number of those. This happens every single year. Even the advanced protections in e.g. Chrome don't stop new vulnerabilities from being found on a regular basis. And all of these products are deployed to millions of users.
You could complain about Apple's response to this bug, and that might be a reasonable complaint to make. At least Google patches bugs quickly when they surface at Pwn2Own. But that's different from claiming the bugs shouldn't have existed (or should have been caught before making it into production). Bugs are fundamentally hard to find, and it's not really getting any easier.