Hacker News Reader

> corruptions of data allocated in the linear memory blocks are susceptible to occur

I don't know if I quite understand this. Is this a web-assembly specific thing, or just the standard C / C++ are "unsafe by default" languages which can cause memory corruption etc because e.g. of off by one errors in pointer arithmetic and so on.

View on HN

The usual stuff with C and C++.

WebAssembly doesn't do bounds checking, besides being in bounds of a linear memory segment.

Basically the access is still in bounds of the allocated memory, but not the cells that one actually wanted to access.

From security point of view, while the WebAssembly module is sandboxes, such corruptions can be triggered from the outside, changing the behaviour of the public API.

Reply on news.ycombinator.com