3 comments

  • tptacek 21 minutes 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.

    • xp84 4 minutes ago
      Should we call it #upcaße2Shell?
      • tptacek 0 minutes ago
        One of the discoverers suggested, on Twitter, Ruby2ßhell. My wife, who speaks and writes German, refused to entertain this.
    • cowlevel 16 minutes ago
      Unicode also has this feature because SS is the correct uppercase form of ß
  • lousken 1 hour ago
    I need a vacation
    • donkey_brains 56 minutes ago
      We all do, but we don’t know if our companies will still be there when we get back.
    • cwmoore 24 minutes ago
      I hear Java is nice
    • _pdp_ 32 minutes ago
      Book it for 18 months from now. Oh, also bring your laptop.
  • TZubiri 33 minutes ago
    It should be pretty straightforward to replace regexes with good ole ifs, array acceses, and comparision operators, whether manually or with an LLM. Pretty low hanging fruit to shave off some kilobytes of attack vector