2 ms·
Any language that lets you call out into third-party libraries not written in that language can end up with heap corruption. The important distinction is that
by kevingadd 14y ago
Any language that lets you call out into third-party libraries not written in that language can end up with heap corruption.
The important distinction is that a 'Nullable' value type need not involve a pointer, which means it can entirely live on the stack, which dramatically limits the damage that can be done by corruption: Worst case, corruption sets the 'hasValue' flag to true, and you read an uninitialized struct off the stack. Much less catastrophic than a double-free or pointer into random memory (Though, of course, a determined attacker could probably make do with either).