Deleted Comment
Deleted Comment
> We reported the vulnerability to Microsoft in April and they have since fixed it as a moderate severity vulnerability. As only important and critical vulnerabilities qualify for a bounty award, we did not receive anything, except for an acknowledgement on the Security Researcher Acknowledgments for Microsoft Online Services webpage.
I guess it makes sense that a poor little indie company like Microsoft can't pay bug bounties. Surely no bad things will come out of this.In the Netherlands we have a system called DigiD to login into to most government websites like your taxes and city, etc.
When I contracted for the city of Amsterdam I learned they’ve been pushing hard for the DigiD app to two factor authenticate instead of text message, because of contracts Digid charges a lot per text message validation and none for app.
There are also just some things you cannot realistically do in the browser (or over SMS) without having to ship specialised hardware to 18 million people, like reading the NFC chip of your passport. This is needed for DigiD Substantieel and Hoog, which are mandated by the eIDAS regulations.
[1] https://github.com/MinBZK/woo-besluit-broncode-digid-app/
On Android, although a built-in isolatedProcess API [1] is available for them to use, there is no sandboxing. No sandboxing on the web in 2025 (!!!). This has been an issue for so many years, yet Mozilla refuses to address it [2]. Chromium does do proper sandboxing on Android, and additionally restricts what syscalls a process can access. Other alternatives, such as Vanadium have even stronger sandbox implementations [3]
On desktop, it's a similar story. Site isolation has had numerous bad issues that haven't been fixed for many years [4][5][6], and especially the Linux builds have had bad sandbox escape vulnerabilities that Chromium is not susceptible to. This is mostly due to architectural differences, like [7] and [8].
The idea of someone being able to take over your computer by just visiting a site is scary. It's beyond me why Mozilla does not prioritise security over yet another sidequest that will slowly bankrupt them.
[1] https://developer.android.com/guide/topics/manifest/service-...
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1565196
[3] https://grapheneos.org/usage#web-browsing
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1505832
[5] https://bugzilla.mozilla.org/show_bug.cgi?id=1484019
[6] https://bugzilla.mozilla.org/show_bug.cgi?id=1707955