Brutkey

Graham Sutherland / Polynomial
@gsuberland@chaos.social

can anyone recall any interesting vulnerabilities in Windows applications that were due to mishandling of character encoding and/or unexpected case sensitivity in file paths? ones with good write-ups strongly preferred.

looking specifically for Windows, specifically character encoding related bugs, and specifically bugs in apps rather than bugs in the OS's own file path handling (e.g. WorstFit)

#infosec

Graham Sutherland / Polynomial
@gsuberland@chaos.social

I am not looking for bugs relating to the handling of file contents.

I'm thinking more along the lines of assuming that file paths are always just ASCII strings, and then getting bitten by UTF-16 path names. or weird cases where two files with the same name but different case exist (e.g. due to FILE_FLAG_POSIX_SEMANTICS) leading to a security issue in an application.

I'm not looking for OS-level bugs like WorstFit.

James Forshaw :donor:
@tiraniddo@infosec.exchange

@gsuberland@chaos.social it feels like something I'd have a write up for, but it seems I've never found anything that useful. There was the whole "you can enable case sensitivity in a directory without privileges" thing MS added but as it was gated behind installing old skool WSL I never found an vuln for it.