4 ms·
I'll say. > Attackers regularly exploit spatial memory safety vulnerabilities, which occur when code accesses a memory allocation outside of its intended bound
by vintagedave 2y ago
I'll say.
> Attackers regularly exploit spatial memory safety vulnerabilities, which occur when code accesses a memory allocation outside of its intended bounds
Isn't that... 'out of bounds memory access'?
- deleted 2y ago[deleted]
- SAI_Peregrinus 2y agoYes. It's as opposed to temporal memory safety vulnerabilities, like use-after-free or data races.
- moyix 2y ago[This is more of a reply to a deleted reply to you, but I don't want my efforts to go to waste] Spatial memory safety is a reasonably common term in the security / PL field. You can see examples of it being used at least as far back as 2009: https://scholar.google.com/scholar?hl=en&as_sdt=0%2C33&q=spatial+memory+safety&btnG= https://scholar.google.com/scholar?hl=en&as_sdt=0%2C33&q=spa... It's in contrast to temporal memory safety, which deals with object lifetimes (use after free, for example). Here Google is probably also referencing a 2022 post of theirs with a very similar title, dealing with temporal safety: https://security.googleblog.com/2022/05/retrofitting-temporal-memory-safety-on-c.html https://security.googleblog.com/2022/05/retrofitting-tempora... The terms are also in Wikipedia: https://en.wikipedia.org/wiki/Memory_safety#Classification_of_memory_safety_errors https://en.wikipedia.org/wiki/Memory_safety#Classification_o...