Re:Pre-auth RCE in Nginx HTTP/2 handling
by AnthonyMouse on Wednesday November 18, 2026 @02:21PM
(#50550781)
Isn't "memory corruption" typically the fast path to RCE? The attacker gets to overwrite a function pointer, or a regular pointer that then lets them overwrite something else, or the length field that will then cause a buffer overrun even in a "safe" language because the run-time length is now different than the one in the compile-time check, etc.
[ Parent
| on HN ]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by tptacek on Wednesday November 18, 2026 @04:06PM
(#50552114)
Memory corruption -> RCE.
Integer handling mistake -> memory corruption -> RCE.
That's the pattern. In a memory-safe language, the integer handling error has no link to memory corruption (though it will to other logic bugs!).