@[email protected] to [email protected]English • 6 months agoJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.comexternal-linkmessage-square22fedilinkarrow-up1185arrow-down18
arrow-up1177arrow-down1external-linkJust about every Windows and Linux device vulnerable to new LogoFAIL firmware attackarstechnica.com@[email protected] to [email protected]English • 6 months agomessage-square22fedilink
minus-square@mindbleachlinkEnglish1•6 months agoHow do you fuck up a bitmap parser? It’s an array. There’s no metadata. You allocate the filesize!
minus-squarebioemerllinkfedilink1•6 months agoIt’s all fun and games until the user has bit rot or some stupid thing is offset by one or a row doesn’t exist somewhere and you have to correct for it
minus-square@mindbleachlinkEnglish1•6 months agoA corrupted bitmap should only look ugly. There is no decoding or compression - only translation, and sometimes not even that. A bitmap is the platonic ideal of a buffer overrun being comically obvious and trivially preventable.
How do you fuck up a bitmap parser? It’s an array. There’s no metadata. You allocate the filesize!
It’s all fun and games until the user has bit rot or some stupid thing is offset by one or a row doesn’t exist somewhere and you have to correct for it
A corrupted bitmap should only look ugly. There is no decoding or compression - only translation, and sometimes not even that.
A bitmap is the platonic ideal of a buffer overrun being comically obvious and trivially preventable.