3 ms·
There are a lot of these (at least there used to be) and that's not only about Chrome. Each browser has its own "fuzzer" and generates crashing HTML all the tim
by flakiness 6y ago
There are a lot of these (at least there used to be) and that's not only about Chrome. Each browser has its own "fuzzer" and generates crashing HTML all the time. Finding these, in a sense, feels more like mining a bitcoin - compute resource matters.
Also, a crash isn't as bad as it appears. Most of the time it's not a security vulnerability. It is only when it involves buffer overrun and the like. They are indeed annoying when you have it in real sites though.
- deleted 6y ago[deleted]
- erk__ 6y agoAnother place this causes issues is with something like Discord which is based on Electron. There have recently been videos and gifs in circulation which crashes the application if watched.
- fulafel 6y agoCrashes are exploitable in many more cases than you'd think, buffer overflows are a minority of them in browsers now.
- MaxBarraclough 6y agoA relevant snippet from the Chromium project [0] > Around 70% of our high severity security bugs are memory unsafety problems (that is, mistakes with C/C++ pointers). Half of those are use-after-free bugs. https://www.chromium.org/Home/chromium-security/memory-safety https://www.chromium.org/Home/chromium-security/memory-safet...
- flakiness 6y agoThat is right. Note that there are many panic-like intentional crashes caused by various safeguards.