@nyanide @dcc It leaks memory, something some Rust programmers refuse to acknowledge that Rust can do.
To be more precise it takes ownership of the argument and forgets it without running it's destructor.
By it self it's basically harmless as you have to call it manually, but it could possibly be leveraged to force a specific heap order that you can then exploit if you find a way to break out of the Rust bounds checking. The chance of this getting exploited in the future is near zero.
=> More informations about this toot | View the thread | More toots from phnt@fluffytail.org
=> View dcc@annihilation.social profile | View nyanide@lab.nyanide.com profile
text/geminiThis content has been proxied by September (3851b).