Re:E2EE on the web: is the web that bad?
by immibis on Tuesday February 20, 2024 @02:13AM
(#39438758)
Indeed Microsoft Teams once contained a bug where specially-formed HTML messages could trigger arbitrary code execution when received.
Any platform where the security model is two steps:
1. Check if the message contains any code. If so, reject it. 2. Scan the message for code and eval() it.
is extremely susceptible to code execution bugs.
Re:E2EE on the web: is the web that bad?
by nightpool on Thursday February 22, 2024 @04:52PM
(#39473797)
Correct. I do not think applications with such a vulnerability should ever be used or marketed as "end-to-end encrypted", since that implies a promise that a malicious or suborned vendor could not be compromise your communications—which, in the case of remotely loaded code, is misleading. I think this is table stakes for any e2ee communication app (e.g. Signal can do this easily since Apple and Google and many third-parties audit their code) but if it conflicts with your current app design, you should be realistic about whether a true e2ee-required threat model can be accommodated by your app.
If that's genuinely part of your threat model, then you simply must run on-premises code only, backed up by robust network controls that allowlist very specific parts of the Internet.