News for hackers. Stuff that matters.
Re:A deep dive into iOS Exploit chains found in the wild by bscphil on Thursday August 29, 2019 @10:56PM (#20835617)
Well, you don't necessarily have to jump from one to the other. If you currently do financial stuff on your phone, just enabling 2FA and only browsing them on your laptop is already an enormous step up. There are cases where additional precautions are warranted, but there's no reason to let the perfect be the enemy of the good.
Re:A deep dive into iOS Exploit chains found in the wild by ikeboy on Thursday August 29, 2019 @11:01PM (#20835638)
Switching from an iPhone to a laptop is a huge step down in security, even with 2FA.

Orders of magnitude more 0-days on whatever software is running on that laptop than on iOS.

This is bad advice.

Re:A deep dive into iOS Exploit chains found in the wild by bscphil on Friday August 30, 2019 @01:29AM (#20836156)
I disagree. 2FA makes it profoundly more difficult to compromise an account. Most people are using a phone as a second factor, so even if the apps don't store files and credentials directly on the device (always in doubt, as seen here), if you have root on a phone you can compromise an account without any user interaction.

What's more, every time you download a banking app on your phone, you have to place a little bit of trust in the competence of whoever the bank outsourced the programming job to. At least with a laptop, a poorly designed website site is not (by itself) a threat to everything on your computer or other sites you visit.

Even when it comes to "more 0-days", I think you're probably missing the point. There's a lot more software written for computers that can be compromised than just the handful of programs that comprise iOS, so the raw count is not very meaningful. More practically, I'm willing to bet the odds my (Linux) laptop is compromised are far lower than my phone. I don't install apps I don't trust on my computer, but I have little choice but to on my phone.

Re:A deep dive into iOS Exploit chains found in the wild by saagarjha on Friday August 30, 2019 @11:00AM (#20839259)
> What's more, every time you download a banking app on your phone, you have to place a little bit of trust in the competence of whoever the bank outsourced the programming job to. At least with a laptop, a poorly designed website site is not (by itself) a threat to everything on your computer or other sites you visit.

Both would require a 0-day exploit to be a threat.

Re:A deep dive into iOS Exploit chains found in the wild by mlyle on Friday August 30, 2019 @02:53AM (#20836442)
> 2FA makes it profoundly more difficult to compromise an account.

Just because the attacks are dumb.

If your computer is pwned, it should wait for you to 2FA, and then when you "log out"-- don't, do malicious stuff instead.

Re:A deep dive into iOS Exploit chains found in the wild by lxgr on Friday August 30, 2019 @07:16AM (#20837513)
That's why 2FA should be performed at transaction confirmation time for sensitive operations, not just at login or periodically.
Re:A deep dive into iOS Exploit chains found in the wild by mlyle on Friday August 30, 2019 @02:07PM (#20841006)
Even then; substitute the transaction they want for another transaction.

If the device you are using is compromised, you're in for a bad time.

You could send some simple transaction summary to the other device to acknowledge, which is getting better. Even so that doesn't completely eliminate the opportunity for tomfoolery.

Re:A deep dive into iOS Exploit chains found in the wild by pastage on Saturday August 31, 2019 @05:38AM (#20845414)
If you sign with a 2FA I can not see how a compromised computer can make that insecure. Though I will say, the UX on 2FA signing needs to get better, but it is secure enough.
Re:A deep dive into iOS Exploit chains found in the wild by mlyle on Saturday August 31, 2019 @12:40PM (#20847344)
If the 2FA doesn't contain the actual transaction detail, pretty simply.

When user tries to transfer $1,000 of cash from user's investment account to user's bank account, instead, initiate transferring $100,000 to EvilGuy's bank account. Rewrite elements so it appears that $1,000 is being transferred to user's bank account, and wait for user to receive their 2FA code and authenticate. This may be as easy as string replacement both ways.

Re:A deep dive into iOS Exploit chains found in the wild by jijji on Thursday August 29, 2019 @11:36PM (#20835789)
maybe in a windows laptop, but people who run laptops using linux probably have more security in the laptop than on their phone, most browsers are pretty safe.
Re:A deep dive into iOS Exploit chains found in the wild by maxdamantus on Thursday August 29, 2019 @11:53PM (#20835854)
I find this hard to believe given that security isn't about "having security", but about "not having buggy software". Unless you're a power user, you're probably mostly just using web applications at this point, so your main target points are the OS and the web browser.

Someone "using Linux" is likely to be running various things such as SSH/HTTP/file servers, native IRC clients, random build systems (running "npm install" instills a lot of trust on the NPM repository and any packages involved). All of these things increase the attack surface.

Re:A deep dive into iOS Exploit chains found in the wild by thenewnewguy on Friday August 30, 2019 @12:17AM (#20835933)
> Someone "using Linux" is likely to be running various things such as SSH/HTTP/file servers, native IRC clients, random build systems (running "npm install" instills a lot of trust on the NPM repository and any packages involved). All of these things increase the attack surface.

This is a fallacy. Rather than assessing the security of the linux kernel or linux distributions you're making taking an assumption about linux users and transferring the blame for their insecure practices onto linux itself.

Think of it this way: If a random Windows user that didn't engage in such behavior was to switch to linux it's unlikely that would suddenly change. If the linux kernel and system programs are more secure than windows that make linux a good choice if that person cares about security.

Note: I'm not making a statement about the security of linux/windows, just pointing out a flaw in the above argument.

Re:A deep dive into iOS Exploit chains found in the wild by maxdamantus on Friday August 30, 2019 @12:35AM (#20836002)
> Rather than assessing the security of the linux kernel or linux distributions you're making taking an assumption about linux users

I was responding to that assumption made by the parent:

> people who run laptops using linux probably have more security in the laptop than on their phone

Re:A deep dive into iOS Exploit chains found in the wild by jijji on Friday August 30, 2019 @12:30AM (#20835984)
The argument from the parent about using a laptop is "orders of magnitude" less safe than using a iOS or android device is just not true. It depends what you're running on each device.
Re:A deep dive into iOS Exploit chains found in the wild by maxdamantus on Friday August 30, 2019 @12:41AM (#20836017)
When you run any given application on your laptop, it's normally run in such a way that it has all of your user's priveleges on the system; that is, it can access all files that you can access, it can look at the screen that you're looking at, it can produce any input that you can produce, it can manipulate the memory of any process that you can manipulate.

When you run an application on iOS or Android, it doesn't have those capabilities. It can only get them through security exploits. In theory it should be similar to looking at a web page. If a web page is able to read arbitrary files, that's obviously a bug in the system. If an application on your laptop is able to read arbitrary files, that's standard functionality.

Re:A deep dive into iOS Exploit chains found in the wild by bscphil on Friday August 30, 2019 @01:40AM (#20836184)
You're right that from a defense standpoint, sandboxed OSes like Android and iOS are "better" than your average laptop. Granted. The point I (and probably your parent comment) were originally trying to make is that the amount of data stored on a phone makes it a very good target for vulnerabilities like these. None of my banking, chat, email, etc information is stored on my laptop because I access these things through the browser. That's not to say that this provides perfect security, of course, but it means someone can't come in with a zero-day that gets root on my system and just one-off uploads all my databases.

Apps that keep all this data locally, as is common on phones, are dangerous. Add the fact that most people have a phone as their two factor and you have a really bad situation when a phone is compromised. This, alone, makes phones an attractive target.

Re:A deep dive into iOS Exploit chains found in the wild by Godel_unicode on Friday August 30, 2019 @10:29AM (#20838950)
> because I access these things through the browser.

Meaning the session cookies are stored on your computer, meaning I can steal those and then do whatever nefarious things I want to do off-box. Locality is a myth, attackers don't care about that. They just want the data, and finding/weaponizing bugs is the hard part.

Re:A deep dive into iOS Exploit chains found in the wild by pjmlp on Friday August 30, 2019 @02:40AM (#20836393)
Regular people keep copies of banking, chat, emails printouts on their "My Documents", even if they use Web applications instead of native ones for those services.

Speaking of native applications, usually many regular users still use native native applications for email, chat, text processing, spreadsheets, etc.

So while you specifically might take care of having a very clean $HOME, most people don't.

Re:A deep dive into iOS Exploit chains found in the wild by pjmlp on Friday August 30, 2019 @12:41AM (#20836020)
Depends pretty much on what they are actually running.

https://www.cvedetails.com/vendor/33/Linux.html

Re:A deep dive into iOS Exploit chains found in the wild by dontbenebby on Thursday August 29, 2019 @11:29PM (#20835752)
Using disappearing messages (eg: Signal) is also good.

If compromised, the attacker doesn't get a long log of comms, just a week's worth.