Login
You're viewing the social.telemetrydeck.com public feed.
  • Oct 22, 2026, 5:10 PM

    I have arrived at a working PoC based on a GitHub repo. But there are signficant caveats. You need 3 precise things to make it work.

    1. Initial offsets for functions are PHP version-specific, so you need those going in. That's annoying but easy.
    2. Heap layout constants based on Zend MM's memory layout for the PHP build. You get this with GDB precisely on a PHP instance you control, or fuzzing a target—messy.
    3. The specific shape of the payload to hit the OOM at the right point. This is largely based on memory limit settings in php.ini.

    So there's some prior work to hit a vulnerable target. A PHP offset "rainbow table" may be somewhere or getting built, but those specifics may explain the lag in clear evidence of exploitation.

    💬 1🔄 3⭐ 0

Replies

  • Oct 22, 2026, 5:21 PM

    @mttaggart This makes it seem like its tricky to use this against, say, furfinity, but practical if you wamted to create one against a deployed device with a consistent PHP configuration, like a firewall.

    💬 1🔄 0⭐ 0
  • Oct 22, 2026, 5:22 PM

    @Epic_Null If you know the PHP version, the attack is annoying but doable. There's also a catch with post size and memory limits. They need to be in a state that the attacker can reasonably hit the OOM.

    💬 0🔄 0⭐ 0