Oh cool, another Chrome 0-day abusing integer overflow.

Neat.

Great.

Awesome.

@thephd this is possibly a controversial opinion, but in my view, integer overflows are _mostly_ dangerous when they cause a “second order” buffer overflow, for instance if the overflowed value is passed to malloc and you get a significantly smaller buffer than you were expecting. If we fix bounds safety, integer overflows aren’t nearly as dangerous as they are today even if we do nothing about them
@fay59 @thephd so long as you don't have overflows when computing your bounds, right? (lol)
@lenary @thephd the beautiful thing about it is that if you do malloc(overflowed_int) and you set the bounds to overflowed_int, you get the right outcome