Comment by gelatocar

8 years ago

Couldn't an attacker construct a page that triggers the memory leak and just keep accessing that page to get different pieces of memory?

Yes. Sign up for service, configure a page with crafted invalid HTML at your origin, activate all three buggy features, and spam it with requests.

If you can find such a page already, just jump to the last step and avoid signing your work.