Of course, @taviso was right about the bs @CrowdStrike crash analysis.
Those who defending the BS analysis made by the "Pro C++ Programmer", Go and take a look at this and gain some knowledge!
mp.weixin.qq.com/s/uD7mhzyRS…
jk 😅
but seriously, with cookies cors and csrf should be taken care of.
Vaya! Parece que el profesional categórico, poco amigo de la diversidad y rápido a la hora de juzgar se equivocó en su análisis de lo de Crowdstrike
No surprises here, but @CrowdStrike confirms @taviso's analysis, that the bug was indeed not due to a NULL-pointer deference 🧠 ...but rather "an out-of-bounds memory read"
Thoughts on @taviso tweet?
No specifics unfortunately, best I have is the report made by CS and this analysis:
Tavio has one of the better breakdowns. x.com/taviso/status/18147623….
Potom tu máme x.com/taviso/status/18147623… ktorý tvrdí, že to nie je NULLptr drf, lebo predtým sa robí test na 0. Lenže termín "NULL pointer dereference" sa nevzťahuje len na hodnotu pointera 0, ale 0+niečo. Obvykle prístup do tabuľky, kde je nesprávna adresa tabuľky.
The original post was x.com/Perpetualmaniac/status… 😳🫣
Here is the analysis @taviso did. Seems like this was an invalid pointer but it’s still not clear to me if this would’ve been prevented with Rust. Think we need to wait for more details.
Here is an analysis that @taviso did of the issue. This might help:
Yeah. But someone actually took time to look at more than one instruction... (so he's incorrect as it's - by thread linked inside - way more likely uninitialized variable in array)
