4 ms·
Zero click hacks have been around for all of computing. Nothing connected to the internet, connected to a network, has ever, ever been safe. All you can do is
by b112 5y ago
Zero click hacks have been around for all of computing. Nothing connected to the internet, connected to a network, has ever, ever been safe.
All you can do is reduce attack surface, and most of all, monitor.
Another comment blames Apple, and financial incentives. Sure, there may be some of that.
But the reality is that safe code is impossible. Now, you may say "But...", yet think about this.
For all of computing history, all of it, no matter what language, no matter how careful, there is always a vulnerability to be had.
Thinking about software, and security any other way, is an immediate fail.
Arguing the contrary, is arguing that the endless litany of endless security updates, for the stuff discovered, doesn't exist.
And those updates oyly cover stuff discovered. There are endless zero days right now, being exploited in the wild, without patches, of which we are unaware.
We're seen vulnerabilities on every kernel, in mainline software, on every platform, sitting for years too. And you know those are discovered by black hats, and used for a long time before being found out by the rest of the community.
Humans cannot write safe software. Ever. No matter what.
Get over it.
Only detailed, targeted monitoring can help you detect intrusion attempts, expose as little as possible, keep updated, and do your best.
- Grimburger 5y ago> safe code is impossible > Humans cannot write safe software. Ever. No matter what. Formally proven code does what it says on the box? Do we have different definitions of safe perhaps?
- speedgoose 5y agoThe proof may be valid but the implementation may have a mistake, or the compiler, or the operating system, or the hardware.
- AussieWog93 5y agoOr if it dynamically loads anything that isn't formally proved.
- mh7 5y agoOne can be fundamentally mistaken about what "it says on the box" See WPA2/KRACK for example. It becomes an infinite recursion of "how do we know the proof of the proof of the..." is what we actually want?
- CorrectHorseBat 5y agobut does the hardware? Formally proven code does not prevent you from hardware bugs like rowhammer.
- b112 5y agoYou mean, when you look at your code, or someone else does, they think it's ok? I guess that's why security issues, even in massively peer reviewed code, are a thing of the past, right? Do your best, code as safely and securely as you know how, peer review and test and fuzz... Then when you deploy your code, treat it as vulnerable, because history days it likely is. Treat your phone as compromised. Anything network connected as compromised. Because history says it can be, and easily. Monitoring is one of the most important security measures for a reason.
- CorrectHorseBat 5y agoThere does actually exist such a thing as formally proven code, which is mathematically according to spec. https://www.sel4.systems/Info/FAQ/proof.pml https://www.sel4.systems/Info/FAQ/proof.pml
- b112 5y agoI don't even see the point you are making. Are you trying to claim that the above proof will never be invaldated? You're really just proving mt point here. You think thongs can be secure.
- kobebrookskC3 5y agowhat do you mean invalidated? the point of proofs is that they will be still be as true today as they will millenia into the future. pythagoras' theorem is just as true today as it was millenia ago.
- CorrectHorseBat 5y agoYes, that's what I'm claiming. That's of course only a part of the story, the spec or the hardware can still be broken.
- bregma 5y agoYou could formally prove Unicode renderers are 100% correct. It's because they are 100% correct that they can be relied on to be exploited. The weak spot when it comes to security is not the hardware or the software, it's the human mind.
- littlestymaar 5y agoYou're missing the point. Humans cannot write bug-free software[1]. Then if you're soft has security-related things to do (like credential management etc.) you cannot be sure there won't be a way to bypass it. But here we're talking almost exclusively about remote execution bugs coming from memory-safety issues, which are indeed preventable. Any managed language does the trick, and if they are not fast enough for your use-case there is Rust. (And, before anyone mentions it, since this isn't some low-level/hardware related thing, you don't need to use unsafe Rust). Rewrites are costly and take time, but we're talking about the wealthiest company on Earth, and this issues has been around for years so they don't really have an excuse… [1]: at least without using formal verification tools, which are admittedly not practical enough…
- b112 5y agoThere is no safe way to code anything, ever. (Yes people, and Apple should try, but...)
- roca 5y agoThis absolutist statement is basically meaningless. Taking Rust as an example (use Swift or even Java if that works better for your use-case), we know how to write Rust code that is guaranteed to be free from common classes of bugs that these zero-click attacks exploit. Yes, we aren't going to get rid of all bugs, yes, zero-click attacks might still be possible once in a while, but we can make it much, much harder and more expensive, and therefore greatly reduce the set of people who have access to such attacks, and reduce their frequency.
- b112 5y agowe know how to write Rust code that is guaranteed to be free from common classes of bugs that these No we don't. You are trying to shift the sands, by saying "But.. this one thing we can do...", except even that isn't true. If we did, it wouldn't keep happening, year after year, decade after decade. But even with peer reviews, with people supposedly knowing how, well.. it just keeps happening. Do you think every occurrence is random chance? Or is it, maybe, just maybe, that humans can't write bug free code?
- egberts1 5y agoApparently, formal proof of algorithms being safe and sound has been repeatedly demonstrated, just not so toward Apple’s closed (proprietary) software specifically their large 14-format image decoders running outside a sandbox.
- xorcist 5y agoWell designed software with attack surface within the bounds of human understanding does not have these problems. OpenSSH has been exposed to the public Internet for over two decades, with nothing resembling this type of security problem. OpenSSH runs the protocol parser without permissions on the local filesystem, yet Apple thinks an ancient tiff library with scripting abilitites can be run with full permissions. Of course there is a discussion of financial incentives and customer expectations to be had here. URL previews are an anti feature for a many users. We could not care less. But it gets shoved upon users by product feature teams for whom a continous stream of new features are their reason for being. That's how we develop commercial software, but that's not the only way.
- Retr0id 5y ago> Apple thinks an ancient tiff library with scripting abilitites can be run with full permissions. It doesn't. That is just one step in a chain of exploits.