5 comments

  • cowlevel 2 minutes ago

    The bug is integer overflow in a random C data-processing library (specifically regexes) leading to RCE.

    Who else is tired of C libraries since this week?

  • JLO64 44 minutes ago

    > Upgrading to GitLab 19.3.6 on October 22 didn’t fix the vulnerability. The fix isn’t in GitLab’s own code but in a patch to Ruby, which GitLab applies only in its official packages. Our image used standard Ruby, so it didn’t get the patch.

    > The bug is in Ruby’s regular expression engine, so any program that compiles regular expressions from untrusted input is exposed, not only GitLab.

    I feel like this era of constant exploits/patches is really bad for those who build from source or make their own images vs those who rely on provided images and upgrade them often. I really can't think of a decent solution for those people other than being plugged in 24/7 to the latest news which is really unfortunate and must be exhausting...

      Gigachad 5 minutes ago

      At this point if you are self hosting you should have everything behind a VPN. Only companies with their own security and development teams should be putting things on the public internet.

      edoceo 38 minutes ago

      The PHP2Shell one was both lucrative and exhausting. I maintain a bunch of legacy PHP apps.

      esseph 41 minutes ago

      It's not maintainable unless you autobuild, and yes, upgrade treadmill.