[oskarsv]

there are different levels of security for ElectronJS, some, like in this case are not enough.

I think it will take a long time before we can call ElectronJS secure. there are regular sandbox escapes and that is from what we know publicly

[untog]

The OP is asking for more detail than “not enough”, though:

“Can it escape the Chromium renderer sandbox? Or is that sandbox disabled?”

[oskarsv]

to simplify - no it’s not enabled

the real answer is more complicated as it is not necessarily a global setting and depends on what you call a “sandbox”

[mwcampbell]

Thanks. I'd pay (moderately) for the more complicated answer. An ebook on Electron security might be a good idea.

[oskarsv]

I'm not an expert on Electron security!

But if not addressed to me, there is no need to pay, you can start here: - https://www.electronjs.org/docs/tutorial/security - https://github.com/electron/electron/security/advisories

As you can see there are plenty of considerations and pitfalls to take into account. Best option is to enable contextIsolation for everything.

Further, Electron security is closely tied to Chrome security so that is one deep rabbit hole

[pjmlp]

Best Electron security is not using it in first place.

[coldtea]

Yeah, let's stick with raw C/C++, that would be much safer...

Or maybe let's use some research language made by Wirth, and get access to all 10 of packages and 5 devs worldwide using it :-)

[pjmlp]

For starters, leave it on the browser.

I didn't mention any programming language.

[gitweb]

Telegram Desktop is a cross-platform C++ app. What similar remote code execution exploit has existed in the wild for it?

[MaxBarraclough]

Rather just keep it in the browser? ;-P

[kevingadd]

This is safer to a significant degree.