This seems like a bad property for a system that encodes human writing systems.
Knight / night is an example for English. That k should be gone, right? Or all those silent -ment and e in French.
Enter the computer and I'm not surprised that German speakers end up mostly with SS because that's what computers do when automatically upcasing words.
A lot of spelling changes are dictated by what's available on keyboards. In Italian we accept E' as È because we don't have that upper case character on our keyboard. Automatic uppercase on start of sentences fixed it where it's available and mobile keywords show an È as an option of you long press a shifted e. But what if you are writing Italian in an English locale form field with a hardware keyboard (here with an OS with English locale) or you have to write È in the middle of a sentence or, go back 30 or 40 years, you have to use a typing machine?
I'm am sure that every language that had to go through a phase of adapting to ASCII and to the limits on the layout of keyboards has similar stories to tell.
Both fixable, but as with a lot of Unicode stuff, might take a long while
Holy sh!t
https://devblogs.microsoft.com/oldnewthing/20200804-00/?p=10...
https://devblogs.microsoft.com/oldnewthing/20241007-00/?p=11...
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.