Earlier quoted context omitted.
iOS does not allow the modification or generation of new executable code (at least, it will not at this stage of an exploit). So they are likely creating a weird machine to patch various data and then redirecting control flow with the altered state by overwriting a function pointer.
Right, and they get there of a decomp pass on totally untrusted input over the network. This is why it's so crazy that apple has this huge attack surface. My own suggestion. Ascii only messages if contact is not in address book or is a contact you've communicated with in your message history (however long you keep that) up to 1 year. Once you reply these untrusted saudi contacts can send you the gif meme's.
A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
171–180 of 360 posts
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#172Earlier quoted context omitted.
Now - that is a big change. Historically the jump from overflow to RCE was much much shorter. Still the iMessage attack surface is just massive and running in an unsafe language kind of crazy?
> Historically the jump from overflow to RCE was much much shorter. Not really. I am about to read the article, but it sounds like return-oriented programming[1] chaining "gadgets" that are small bits of existing code that you can re-purpose into executing arbitrary code by manipulating the stack. Extremely common exploitation technique, even if not trivial. Who said an exploit or RCE was trivial to exploit? Edit: I…
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#173This is quite clever, but fundamentally it's only possible because of a buffer overflow. If the JBIG decoder had been written in Rust (just to cite one example of a language safer than C), this would have been impossible. Use dumb languages, pwn valuable prizes.
Edit: instant flagged for commenting anything non-positive about the Rust evangelism cult
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#174Earlier quoted context omitted.
The problem with nation states is that they don't pay people. I don't think nation state can ever come up with something like this - it takes passion, genius and those qualities demand higher premiums than governments are ever willing to hand out.
Their entire business model is predicated on nation-states paying NSO more than NSO pays their employees.
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#175This negligence is killing journalists and activists.
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#176Earlier quoted context omitted.
The problem with nation states is that they don't pay people. I don't think nation state can ever come up with something like this - it takes passion, genius and those qualities demand higher premiums than governments are ever willing to hand out.
Their entire business model is predicated on nation-states paying NSO more than NSO pays their employees.
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#177Earlier quoted context omitted.
Is proving P = NP equivalent to knowing how any intractable problem can be solved? Is it possible for P=NP and yet a class of intractable problems to remain unsolved?
It would mean that a large class of problems that have solutions that can be verified quickly can be solved quickly. Which cuts both ways. While that means most protocols used for cryptography would need to be replaced (hashing, digital signatures, etc) it also means other combinatorics algorithms (traveling salesman, protein structure prediction) would become solvable which may been boon for logistics and/or computa…
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#178Earlier quoted context omitted.
A large percentage of the planet has personal sensitive data stored by Google. If that data leaks, even due to a bug in another company's product through which Google has no fault, Google suffers. Google greatly benefits by having a secure Internet.
On this note, has google ever had a breach? I actually can't think of one off the top of my head, which is impressive for a company like google with so much data and such a large footprint Either their security or PR is great (or both?)
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#179Earlier quoted context omitted.
Enhancing works with trained AI these days Maybe not for evidence collection, but for pleasing a human being to go follow a lead sure
I've seen some examples of this. It's very clearly trained on a white-male dataset. I've also seen it "enhance" an image of a resistor into a human face. I don't care how much AI you have, you can't add back data that wasn't in the original image. The best you can hope to do is get a vague approximation, and you must have a very, very good (comprehensive) training dataset for that to be remotely viable.
TBF the Beatles look amazing in the Peter Jackson documentary, though the original material was shot on 16mm.
Re: A deep dive into an NSO zero-click iMessage exploit: Remote Code Execution
#180From the top of the article: > We want to thank Citizen Lab for sharing a sample of the FORCEDENTRY exploit with us, and Apple’s Security Engineering and Architecture (SEAR) group for collaborating with us on the technical analysis. This reminded me that NSO went after Citizen Lab on multiple fronts. They even tried to use a spy to talk to JSR ( https://www.johnscottrailton.com ) and make him say controversial things…
The transcript is such an intriguing read. You don't expect these things to happen in real life, but yet here they are, tie-cameras, pen recorders, driving circles around the block and all.