Remix.run Logo
▲ Ruby2ßhell: Pre-authentication RCE on stock Rails(verialabs.com)
155 points by jdns 6 hours ago | 58 comments
▲cowlevel an hour ago | parent | next [-]

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.

▲aja12 41 minutes ago | parent | next [-]

It's important to note that Java, like Rust, is generally seen as a memory safe language. But it has bits of assembly, just like Rust has unsafe blocks, to handle some operations. Hence the Java2shell recent vulnerability. Granted Rust may have less need for them and more facilities to audit them, but it is not by itself a panacea that will fix all memory issues. In essence, there is no software stack that is fully memory safe, it is more a matter of restricting the memory unsafe parts in fewer, more scrutinized, better contained sections.

▲ninkendo 16 minutes ago | parent | next [-]

OP didn’t say anything about Rust, by the way. This post comes off as being defensive about a point nobody made.

▲zamadatix 34 minutes ago | parent | prev | next [-]

Yeah, "memory safe" goes out the window if you prefer to implement parts in assembly. This is where portable SIMD (e.g. the Java vuln was from SIMD), which is abstracted & safe but not necessarily as performant as it could be, is becoming a more reasonable trade off.

Of course I'm not sure how much it counts to be "using a memory safe language" when you have to call put to unsafe code anyways. I.e. just because the library you'd like to use is C but the rest of your project is Rust doesn't mean you're really using a me ory safe language, it means you're sometimes using one. We have a long way to go before environments allow using memory safety fully I think.

▲anthk 24 minutes ago | parent | prev [-]

Rust it's far better than Java. Since the old times Java was seen as a CVE generating machine for GNU/Linux environments.

▲toastal an hour ago | parent | prev | next [-]

I like your comment since it points out that we need to enforce the memory situation—but it doesn’t prescribe Rust is the only solution.

▲boomlinde an hour ago | parent | prev | next [-]

From my understanding it's only a single byte overflow if your payload only contains a single ß.

▲yuliyp 5 minutes ago | parent [-]

From the pseudocode it's always a single byte. Desyncing before the end of the buffer is fine. Desyncing at the very end causes the single byte overflow.

▲miohtama an hour ago | parent | prev | next [-]

This is bad news for C/C++

▲xnickb an hour ago | parent | next [-]

This is bad news for computer industry. See the recent Java4Shell.

▲eecc an hour ago | parent [-]

because the assembly for the base64 decoding was handwritten, the paren't comment is still valid

▲dingaling911 37 minutes ago | parent [-]

I think the point is that the weakest link WILL be found.

▲anthk 23 minutes ago | parent | prev [-]

At least C folks can use something like BoehmGC and calm down things a little.

▲trismegisti an hour ago | parent | prev [-]

But are those generic exploits, that don't rely on specific dynamic library and kernel versions? i doubt it.

▲zamadatix 9 minutes ago | parent [-]

The problem now is it really doesn't matter as much. Before you had to put the work in to make the exploit chain work in the specific situation. Now you just need the entry point through the narrow hole in the exposed portion and a target set worth the tokens to customize it to work against one of the individual deployments. At least until we get better at making it difficult to chain things in response.

▲circularfoyers 3 hours ago | parent | prev | next [-]

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).

▲barbegal 2 hours ago | parent | prev | next [-]

More interested to see how you can use just a single byte overflow to trigger RCE. Definitely achievable but sounds tough.

▲enjoytheview 4 minutes ago | parent | next [-]

The next byte in the heap might be the size of an allocation, so if you overwrite it and then free that other allocation, the heap code will think that there is a very large free area there instead of a small one, once you allocate that, you now have a very large heap overflow and can do more fun things. That is just one idea, there are many other ways.

▲deprave an hour ago | parent | prev [-]

There was an article on this topic in Phrack 55 back in 1999: https://phrack.org/issues/55/frame-pointer-overwriting#artic...

Exploitation conditions are likely more challenging today but that’s the earliest reference I know for exploiting a single byte overflow.

▲valleyer an hour ago | parent [-]

The commit message for the Ruby fix says it's a heap buffer, so frame pointer smashing would not apply here.

▲weinzierl 3 hours ago | parent | prev | next [-]

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.

▲stuxf 3 hours ago | parent [-]

this relies on specific behavior with how the upcase function worked, the ß is the only one that expands in a way that works for this vulnerability.

▲weinzierl an hour ago | parent [-]

Can you elaborate on what makes ß special enough to enable the vulnerability.

A quick search showed that there are other cases in legacy encodings that expand to multiple bytes.

For example 0xEF in ISO 6937 expands to CA BC 4E in UTF-8 after case transformation. Similar to ß this is a case with a single byte legacy encoding with a single lowercase unicode codepoint which has no precomposed upper case equivalent.

▲debugnik an hour ago | parent [-]

From the Ruby docs:

> Non-ASCII case mapping and folding are supported for UTF-8, UTF-16BE/LE, UTF-32BE/LE, and ISO-8859-1~16 Strings/Symbols.

ß might actually be the only character that expands to multiple bytes on the original encoding from that list of ISO encodings.

▲weinzierl an hour ago | parent [-]

Ah, good point. If ISO-8859-1 is the only supported single-byte legacy encoding then ß is most likely the only case.

EDIT: Thinking about it, my example from above should work with UTF-16 input.

U+0149 is a single lower case BMP codepoint, so two bytes in UTF-16. It has no precomposed uppercase, so it turns into two codepoints and 4 bytes in UTF-8 and UTF-16.

▲Panzerschrek 3 hours ago | parent | prev | next [-]

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.

▲johnp_ 2 hours ago | parent | next [-]

There was never any guarantee that case conversion is byte length equivalent. Except for pure ASCII, that's just been an incorrect assumption from the start.

▲debugnik an hour ago | parent [-]

This only affects ISO-8859-1~16 encodings, Ruby only supports non-ASCII case folding for those and UTF. It might actually be the only character from that list of ISO encodings for which the length changes.

▲rob74 2 hours ago | parent | prev [-]

Ah, so that's the real reason "ß" is now allowed in uppercase too (https://en.wikipedia.org/wiki/%C3%9F)? Reducing the risk of security issues by removing an edge case?

▲pwdisswordfishq 2 hours ago | parent | next [-]

The Unicode case mappings are covered by backwards-compatibility guarantees. "ß" is going to be mapped to "SS" forever.

▲cubefox 2 hours ago | parent | prev [-]

It even seems the "more correct" uppercase form of ß is now ẞ, not SS.

> Traditionally, ⟨ß⟩ did not have a capital form, and was capitalized as ⟨SS⟩. Some type designers introduced capitalized variants. In 2017, the Council for German Orthography officially adopted a capital form ⟨ẞ⟩ as an acceptable variant, ending a long debate.[4] Since 2024 the capital has been preferred over ⟨SS⟩.[5]

▲shevy-java an hour ago | parent [-]

> It even seems the "more correct" uppercase form of ß is now ẞ, not SS.

But that is wrong. In german I only know of ß aka downcased version.

ẞ seems another character. I have no idea what it is, other than looking close to ẞ, but it most assuredly is not existing in the german language. There is simply no uppercased variant. 'ss' is "Doppel-s' - that is not ß. In german we have "das" (which is the), but it can be "das" or "dass" depending on the sentence, in particular after a ',' character. I often misspell it, since I prefer "das", when in reality sometimes one has to use "dass". But 'ß' is very different to that - to claim that 'ß' is equivalent to 'ss' is simply incorrect. I have no idea who that "Council for German Orthography" is, but clearly they don't know anything about German. Who put that Council in charge of anything? Are these drunks? The claim that the capital has been preferred, is also factually wrong. Who is writing all that?

Edit: Oh I see, you have that from Wikipedia.

The .pdf can be found here:

https://www.rechtschreibrat.com/DOX/RfdR_Amtliches-Regelwerk...

So from what I can see, this is only the:

"Leibniz-Institut für Deutsche Sprache"

That is not a unified authority for anything. It is totally unclear to me why the wikipedia article claims that this is legally binding for anyone. That's just factually incorrect. Is Wikipedia no longer proofreading?

▲cubefox 7 minutes ago | parent [-]

Wikipedia says ẞ is "preferred", which is plausible when an organization with an impressive name declares it preferable. Nobody says it's legally binding.

> I often misspell it, since I prefer "das", when in reality sometimes one has to use "dass".

It's confusing because both can mean "that".

"That is true." = "Das ist wahr."

"He said that it is true." = "Er sagte, dass es wahr ist."

▲speedgoose 2 hours ago | parent | prev | next [-]

But can the attacker specify the encoding in rails? It's not like UTF-8 or GTFO?

▲CER10TY 2 hours ago | parent [-]

You can freely specify the encoding when sending multipart/form-data POST since Rails respects the charset attribute in Content-Type, eg Content-Type: text/plain; charset=Windows-1252

▲bloak 2 hours ago | parent [-]

So you have to convert ISO-2022-JP, for example? That sounds like a disaster waiting to happen.

▲lmz 2 hours ago | parent [-]

Clients have to do the same with server responses.

▲zelphirkalt 3 hours ago | parent | prev | next [-]

Name as discussed earlier here on Hackernews :) Glad they went with that name.

▲gsich 2 hours ago | parent | prev | next [-]

no poc. go away.

▲stuxf 2 hours ago | parent | next [-]

would you rather we publish a PoC for a vulnerability that doesn't even have a patch yet? e.g self-hosted GitLab still hasn't shipped a newer version of Ruby that's patched...

would be wildly irresponsible

▲oguz-ismail2 an hour ago | parent [-]

>we

I doubt you have a PoC at all

▲spikewall 2 hours ago | parent | prev [-]

took glm a bit over 20 minutes to write one, based on the report.

▲sgt 2 hours ago | parent | prev | next [-]

Django next? Although it's unlikely, Django is known to be above average in terms of security by now.

▲Gigachad 2 hours ago | parent | next [-]

The bug here is in the C code for Ruby. Python is also written in C and just as likely to have memory bugs.

▲pjmlp 2 hours ago | parent [-]

CPython.

▲imtringued 2 hours ago | parent | prev | next [-]

The days of people feeling secure because they don't make egregious mistakes are unfortunately over. Now the rule is: You are vulnerable, you just don't know how.

▲DarkNova6 2 hours ago | parent | prev [-]

Above average doesn’t cut it these days. And doesn’t Python have some of the strongest exposures to C libraries?

Well…

▲sgt an hour ago | parent [-]

Uh oh. I guess it's being hammered with people with Red Team access right now.

▲pluc 9 minutes ago | parent | prev | next [-]

Here come the united statesmen asking about Ruby 2b hell

▲phil294 5 minutes ago | parent | prev | next [-]

Fortunately, Rails' creator DHH recommends to use Rust nowadays anyway. https://www.youtube.com/watch?v=vDjW_dRyKXY

▲wiether an hour ago | parent | prev | next [-]

Get ready to upgrade your GitLab instance...

▲lousken 3 hours ago | parent | prev | next [-]

Scheiße2Shell?

▲tvvocold 2 hours ago | parent | prev | next [-]

One Shell a Day, Ops Run Away.

▲rs_rs_rs_rs_rs 3 hours ago | parent | prev | next [-]

For once a bug name that's cool.

▲stuxf 3 hours ago | parent [-]

we were thinking of naming it ruby off rails haha, but this title ties into how this vulnerability works which was super cool

▲rs_rs_rs_rs_rs 2 hours ago | parent [-]

And the fact that you can almost read it ruby 2 hell

▲realsdx an hour ago | parent | prev [-]

Another day, another RCE!

▲srgb_vs_cmyk 37 minutes ago | parent [-]

It is getting absurd, in span of 48h there is one for nginx, java, php and ruby; with another one for php and ruby in last month.