Re:Pre-auth RCE in Nginx HTTP/2 handling
by tptacek on Wednesday November 18, 2026 @11:54AM
(#50548674)
No. Memory safe languages still have integer handling issues, but the consequences are different. In a memory-unsafe language, integer mishandling often nets out to bad copies and memory corruption.
[ Parent
| on HN ]
Re:Pre-auth RCE in Nginx HTTP/2 handling
by vlovich123 on Wednesday November 18, 2026 @12:01PM
(#50548780)
I wouldn’t be sure that a Rust equivalent would be immune because it’s not hard to imagine an underflow/overflow from reaching an unsafe block that’s used for performance (the implicated TLS path would be a hotspot worthy of such a choice).
Re:Pre-auth RCE in Nginx HTTP/2 handling
by tptacek on Wednesday November 18, 2026 @12:04PM
(#50548818)
This is the thing about `unsafe` blocks: they're not memory safe. It's right there in the name.
Re:Pre-auth RCE in Nginx HTTP/2 handling
by vlovich123 on Thursday November 19, 2026 @12:01AM
(#50556247)
Android had an integer overflow vulnerability where it could be tricked into verifying the signing of one file but install another for execution. Boeing 787 Dreamliner had a bug where after 248 it's 32-bit counter overflowed triggering a "fail-safe" mode that shut down all electrical power to the aircraft.
You're right it's more rare but the results can still be catastrophic.
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.
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!).