News for hackers. Stuff that matters.
Re:Serious Chrome zero-day by yayr on Wednesday March 06, 2019 @04:02PM (#19322764)
What does this mean for Electron Apps?
Re:Serious Chrome zero-day by AgentME on Wednesday March 06, 2019 @04:21PM (#19322917)
If the Electron app never shows untrusted HTML with Javascript enabled, then it's not an issue. Generally, only Electron apps with arbitrary web browsing functionality would do that.
Re:Serious Chrome zero-day by cjones26 on Wednesday March 06, 2019 @04:37PM (#19323105)
Which is a massive security issue in itself--Electron documentation even warns you about this.
Re:Serious Chrome zero-day by AgentME on Thursday March 07, 2019 @02:50PM (#19331558)
Electron's docs (https://electronjs.org/docs/tutorial/security#isolation-for-...) mention that you should webview or BrowserView with a certain option with untrusted content, not that it shouldn't be done at all.
Re:Serious Chrome zero-day by nickysielicki on Wednesday March 06, 2019 @04:36PM (#19323090)
Do most Electron apps make use of CSP? eg: is it an inherent part of the build process, or is it something that the developer needs to explicitly add?
Re:Serious Chrome zero-day by hartator on Wednesday March 06, 2019 @05:52PM (#19323798)
The thing seems to be linked to FileReader. Maybe just linking to an external image is enough.
Re:Serious Chrome zero-day by idlewan on Wednesday March 06, 2019 @08:00PM (#19324683)
FileReader is not related to an image tag loading its image, it's a javascript API: https://developer.mozilla.org/en-US/docs/Web/API/FileReader

So attacker would still need to have some javascript loaded somewhere for it to work. If electron app displays user-generated content, XSS can help run a javascript payload, however.

Re:Serious Chrome zero-day by dleslie on Wednesday March 06, 2019 @04:12PM (#19322841)
They are very likely to be vulnerable.
[dead]
Re:Serious Chrome zero-day by bezosbaldballs on Wednesday March 06, 2019 @04:37PM (#19323100)
> uses up all your resources > is enormous in size for no reason > javascript

Ok, agreed.