upvote
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

reply
the patch is to update ruby
reply
deleted
reply
>we

I doubt you have a PoC at all

reply
took glm a bit over 20 minutes to write one, based on the report.
reply
RCE or crash?
reply
crash, https://pastebin.com/y3WQEcSU - for rce you will need a bit more time/tokens.
reply
Does every crash prove that a RCE can exist? This sounds halting problemy.
reply
No, every crash does not prove an RCE can exist. However certain types of crashes are smelly enough that it's safest just to assume that someone, somewhere, on some system can probably lift it into an exploit.

If you are not calibrated with how small a hole it can take to lift a system up into full code execution, I recommend budgeting a couple of hours to spend with https://projectzero.google/2021/12/a-deep-dive-into-nso-zero... and https://projectzero.google/2022/03/forcedentry-sandbox-escap... . I think way too many developers still don't grok what hackers can do, even before AIs. They too often think just in limited terms about the hole itself without understanding where the holes can lead.

I've red teamed some systems locally, and I've found rather a wide variety of issues that I couldn't actually work into a working exploit, either at all or in any reasonable manner that didn't require me to very carefully configure a system in an unrealistic manner just so it could be exploited, but even at a much smaller scale you really just want to fix them rather than worry about them. Defense in depth if nothing else.

reply
The authors say that the vuln allows RCE and they will publish a PoC in a week
reply