I am a recent grad, tbh i do not know to code and have only vibecoded bs. I actually never saw projects to end and just initial vibe codes. Now that i graduated i realised how fucked i am.
I am unable to decide what to learn n now. Do i learn manual coding so that i can build stuff without ai and then use ai to accelerate. Or do i just learn to prompt better somehow. But how do i prompt better if i do not know what direction do i take the project apart from the vague output i have in mind. How do i get engineering part
I really struggle how you can do remote code execution by writing a single, predetermined byte out of bounds. Can anyone explain that to me? I just don’t see how this is realistically exploitable?
You can control the length of the buffer. This means that this is a primitive for writing one byte at a time, from finish to start. It is likely difficult to set up a shell using this, unless you are keenly aware of the memory layout on the server. My guess is that you'd have to rely on some coincidence between the letters 'S' and 's' and some architecture's bytecode.
It's possible the exploitability is overstated. People are prone to that. It may be exploitable only under hypothetical or unrealistic conditions. You might be surprised, though.
Unfortunately this is where AI excels. These types of issues used to be flagged as lower priority issues because on careful examination from expert devs, they couldn't see a way it could be exploited.
It's not one byte. It's one byte per ß. The writeup says the buffer is allocated as len + 20, so you need 21 ßs to overflow 1 byte. Make that "ß*100<payload>", and you've pushed your payload 80 bytes past the buffer.
Its confusing, because looking at the code snippet itself it appears like the while(to<to_len) check iterating through each character would still only allow this the be a single byte overflowing the very last iteration.. since the *to++ is happening/incrementing 2 times each loop to keep the check (except for the very last one)
Yeah I'm sceptical too. It's probably possible in some way or another, but it's also "CVE pending" so there's no score however flawed those scores may be.
But better give it a 2shell name for some attention before the risk factor is even evaluated.
We'll be publishing a proof of concept demonstrating remote code execution on stock Rails on 25 November 2026, or later if major vendors have not shipped a fix by then.
Hi, I work for the Open Source Security Foundation (OpenSSF) on security. It's *possible* it isn't really exploitable. However, that is *not* where I would place my bet. This kind of vulnerability (ability to write a single byte out of bounds at will) has turned into practical exploits before, so attackers already have patterns to learn from, and the best AI models are now *really* good at chaining together "minor defects" into a full remote code execution (RCE). I think the "right thing" to do now is to make it *easy* to update your software (including your dependencies) and make sure it passes a good test suite. If you get an update that says "please update for this vulnerability, I've already verified your thorough test suite passes", it's easy to accept. If you have to do a lot of manual analysis, you've already lost before you begin. There are going to be a LOT more vulnerabilities found in software. Now is the time to get ready for the updates.
79
u/Pierma 2d ago
I just had a painful 16 production machines update day becuase ß uppercased is SS??????????
310
u/razialx 2d ago
And you get a 2shell! And you get a 2shell!!! Everybody gets a 2shell!!!!!!
51
u/RustOnTheEdge 2d ago
I really struggle how you can do remote code execution by writing a single, predetermined byte out of bounds. Can anyone explain that to me? I just don’t see how this is realistically exploitable?
19
u/arcrad 2d ago
DeezNuts2Shell
7
u/sblinn 2d ago edited 1d ago
Destination: hell
Ruby ruby ruby ruby 2 shell
15
u/ScottContini 2d ago
WARNING: Do not enter https://ruby2shell.com in your browser. Just don’t do it.
2
u/maifee 1d ago
Waiting for shell2shell now
4
u/zombiecalypse 2d ago
2shells1cup
1
u/this_knee 2d ago
Oh come on!
1
u/Darmo_ 3h ago
ßhell lol someone doesn't know what ß is