Need help?
<- Back

Comments (155)

  • cowlevel
    So the recent RCE wave seems to be people finding more single byte overflows and such, but reporting them as RCEs because AI can do the tedious grunt work of finding the rest of the vulnerability chain.If any single byte overflow can be converted into an RCE with minimal human effort then we have no choice but to prove the whole software stack is memory safe.
  • circularfoyers
    Thought this was another vulnerability for a second, but for anyone else who thought the same, this is already covered in the Ruby advisory being discussed here https://news.ycombinator.com/item?id=50554038 (which covers six other vulnerabilities).
  • djha-skin
    I remember being a kid in a small town. My dad got into an auto accident, and the next day the DJs talked about it on the radio. Then we moved to the Chicago area and the morning news only ever talked about how many accidents we'd see that day on our theoretical morning commute during the traffic segment.At what point will we stop considering individual x2shell ultra-critical CVEs news in the age of AI? Like, how many of these are we finding per hour?
  • barbegal
    More interested to see how you can use just a single byte overflow to trigger RCE. Definitely achievable but sounds tough.
  • t1234s
    For people who haven't been to Germany the character that looks like a script B is pronounced like "S". Its a bit of humor in what is an annoying problem.
  • anon
    undefined
  • Panzerschrek
    I suppose this function has been written first in assumption, that case conversion doesn't affect length, but later ß -> SS conversion has been added without proper testing.
  • weinzierl
    There should be other codepoints other than ß that in principle could be used for a vulnerability like that. There are even ones that expand to three codepoints, like ffi.
  • GTP
    > We'll be publishing a proof of concept in a week, once people have had time to upgrade.I think one may now decide to publish the PoC straight away or not publish it at all, since an AI agent pointed at this post would very likely be able to produce one in a few minutes.
  • speedgoose
    But can the attacker specify the encoding in rails? It's not like UTF-8 or GTFO?
  • zelphirkalt
    Name as discussed earlier here on Hackernews :) Glad they went with that name.
  • olejorgenb
    I assume Gitlab.com run a fixed version, but it would be good if they could confirm it now..
  • shipsafestack
    [flagged]
  • FreeBurn
    [flagged]
  • binarybriefing
    [flagged]
  • francuza9
    [dead]
  • lousken
    Scheiße2Shell?
  • wiether
    Get ready to upgrade your GitLab instance...
  • tvvocold
    One Shell a Day, Ops Run Away.
  • neko_ranger
    we Germans already have a word for this, we call it ruby2ßhellen
  • rs_rs_rs_rs_rs
    For once a bug name that's cool.
  • pluc
    Here come the united statesmen asking about Ruby 2b hell
  • anon
    undefined
  • phil294
    Fortunately, Rails' creator DHH recommends to use Rust nowadays anyway. https://www.youtube.com/watch?v=vDjW_dRyKXY
  • realsdx
    Another day, another RCE!
  • slekker
    DHH in shambles
  • ajainvivek
    [flagged]
  • lost_pointer_an
    [dead]
  • EINFLUSS
    [flagged]
  • sgt
    Django next? Although it's unlikely, Django is known to be above average in terms of security by now.
  • gsich
    no poc. go away.