| ▲ | tptacek an hour ago | ||||||||||||||||
There's what I think is probably an awesome bug here. Windows-1252 encoding has a representation for lowercase German sharp 's' (ß), but not one for the uppercase. If you upcase a string containing a sharp 's', it gets normalized to "SS", which increases the length of the string by one character. The 1252 case conversion code doesn't handle this; it looks like it checks for headroom in the buffer one character at a time. So if the last character of a string you upcase is ß, it looks like you get a one-byte overflow (of 'S'). If that's really the bug (there's a claimed RCE POC), the heap grooming for it must be really fussy! I couldn't find any other character pairs that expand like this. You can feed strings in 1252 to a Rails program through multipart POSTs, which get to pick their encodings. The great thing about this bug, apart from how it illustrates how doomed we all are (if I'm right), is that it should by rights have the best vulnerability name of the year, because you get to work 'ß' into it. | |||||||||||||||||
| ▲ | testplzignore an hour ago | parent | next [-] | ||||||||||||||||
I wonder if there is a similar bug for U+0130 which (I think) expands to two characters when lowercased. | |||||||||||||||||
| |||||||||||||||||
| ▲ | bee_rider 30 minutes ago | parent | prev | next [-] | ||||||||||||||||
Haha, that exact character caused problems in a programming class I tutored for. Got to throw the first year students some curveballs. | |||||||||||||||||
| ▲ | xp84 an hour ago | parent | prev | next [-] | ||||||||||||||||
Should we call it #upcaße2Shell? | |||||||||||||||||
| |||||||||||||||||
| ▲ | cowlevel an hour ago | parent | prev [-] | ||||||||||||||||
Unicode also has this feature because SS is the correct uppercase form of ß | |||||||||||||||||
| |||||||||||||||||