Live data from Hacker News

Coinbase: Responding to Firefox 0-days in the wild

blog.coinbase.com

11–20 of 97 posts

Re: Coinbase: Responding to Firefox 0-days in the wild

#11
post #9

Does it a help in this case if one runs the browser in a sandbox? E.g. in docker? They can then break out from the browser, but only get to docker with that exploit, and it's unlikely they have a docker exploit too at hand, is it?

Having two 0-days for one of the most popular browsers tells me they probably have access to whatever they want.

Re: Coinbase: Responding to Firefox 0-days in the wild

#12
post #9

Does it a help in this case if one runs the browser in a sandbox? E.g. in docker? They can then break out from the browser, but only get to docker with that exploit, and it's unlikely they have a docker exploit too at hand, is it?

Having two 0-days for one of the most popular browsers tells me they probably have access to whatever they want.

For high value targets, probably. For average spear phising I don't think they spend more resources to break out from docker.

Since default docker runs linux, running the browser in a linux docker can be enough, because they usually have windows exploits.

Re: Coinbase: Responding to Firefox 0-days in the wild

#13
post #9

Does it a help in this case if one runs the browser in a sandbox? E.g. in docker? They can then break out from the browser, but only get to docker with that exploit, and it's unlikely they have a docker exploit too at hand, is it?

They can then break out from the browser, but only get to docker with that exploit, and it's unlikely they have a docker exploit too at hand, is it?

If you are running Firefox on X11 (which most Linux users probably still do), you do not need to escape Docker. You can make screenshot, capture keystrokes, and send keystrokes, all through the X11 socket.

(Furthermore, you do not need a Docker exploit, a Linux kernel exploit can be enough to break out of a container. This is one of the reasons for e.g. gVisor to implement syscalls in userland and in a safer language.)

Using VMs as e.g. Qubes OS does is probably a bit safer than a Docker container.

Re: Coinbase: Responding to Firefox 0-days in the wild

#18
This point to an actual use of the cryptocurrency - exploiting a 0 day against someone who might have a crypto wallet means you can actually directly make money off exploits. Prior to crypto, having a 0 day wasn't equal with ability to make blackhat money with it...

Re: Coinbase: Responding to Firefox 0-days in the wild

#19
post #10

Coinbase should be hiring pentesters and giving them employee level access - even access to commit and deploy code. Any insider shouldn't be able to steal more than the hot wallet, and even that should be hard. I actually wouldn't put much effort into border security. At coinbases level of risk, evildoers will have no qualms bribing an employee to install a backdoor in their machine.

The trouble is finding someone to bribe who won’t suddenly start buying new things.

To follow through on that though, what makes you think that would be anything noticeable? Suddenly a coinbase employee buys a cool car or other new toy... So what? Nobody would think that was exceptional.

Re: Coinbase: Responding to Firefox 0-days in the wild

#20
post #10

Earlier quoted context omitted.

The trouble is finding someone to bribe who won’t suddenly start buying new things.

To follow through on that though, what makes you think that would be anything noticeable? Suddenly a coinbase employee buys a cool car or other new toy... So what? Nobody would think that was exceptional.

I think this is why investigations require low levels of evidence to start, but high levels of evidence to end.

Just because it isn’t exceptional doesn’t mean that it isn’t worth looking into. People who are greedy are impulsive and are unlikely to hide an inflow of cash.

Post reply on HN