Login
You're viewing the social.nerdzoom.media public feed.
  • Oct 21, 2026, 9:19 PM

    - I have upgraded my servers to fix the PHP bug.

    - But I have not yet re-enabled them, as no one can explain how to test whether the update successfully protected me from the exploit.

    - In the meanwhile, two people on Mastodon are trying to convince me there are other, unnamed live PHP vulnerabilities which remain unpatched, and it is unsafe to bring my site up even if today's two vulns are fixed.

    social.arthfach.com/@arthfach/

    - Are they full of shit?

    💬 1🔄 0⭐ 0

Replies

  • Oct 21, 2026, 9:21 PM

    @mcc Fedi is the first point of info now so while I don't know I'd act on it specifically, I wouldn't ignore it.

    💬 0🔄 0⭐ 0
  • Oct 21, 2026, 9:33 PM

    @mcc there has been zero disclosure from what I read. Just some hinting that someone found a thing.

    💬 0🔄 0⭐ 0
  • 💬 2🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Oct 21, 2026, 10:00 PM

    @chillicampari @elebertus Now, I'm not what I'd consider an infosec specialist, and i'd obviously prefer to fix all double frees promptly, in fact I'd. But "double free found" does not as far as I know. necessarily equate to RCE. My non-specialist impression would be that is a "risk of RCE exists". There are even in fact multiple ways of building an executable hardened so that double free by itself is harmless.

    💬 1🔄 0⭐ 0
  • Oct 21, 2026, 10:07 PM

    @mcc sure! But a lot of this is poking things with a stick to see what wiggles. You don't have to act on it but it's good to know it's there (so, not total bullshit). If it's a real thing it will be assigned a number and actionable measures but for now it's something you can keep an eye on if you want. I would actually still release/reopen at this point but it is up to each person with admin privileges to decide. @elebertus

    💬 0🔄 0⭐ 1