Somebody has leaked CVE-2026-109618 and CVE-2026-109619 in PHP before the patch is out.
-
A really good mitigation for this btw - AppArmor or SELinux.
Google something like apparmor restrict php from executing commands. Works against these CVEs.
Sucks for cybersecurity vendors who shipped their appliances using PHP without SELinux or AppArmor, of course.
@GossiTheDog
deny /usr/bin/id x
Systemwide protection against all exploits
-
If you use Palo-Alto firewalls, make sure you upgrade for the PHP vulns.
In particular, if you have the mgmt interface facing the internet upgrade those now. The Palo-Alto firewall VMs have ASLR disabled which makes exploitation trivial.
For anyone else looking for PaloAlto's notice, it's here:
https://security.paloaltonetworks.com/CVE-2026-109618I'm waiting for it to say something other than ETA: TBD
Had a hard time finding it initially because google wants to send you to their unit42 writeup that covers their take on them protecting you from everyone else instead.
-
Also hp system management homepage (installed on HPE Proliant servers) all ship with PHP.. with no ASLR. There doesn’t appear to be a patch for that, you can use it to surf around flat networks as it drops you as SYSTEM/root.
@GossiTheDog wasn’t that on Gen9 servers only which are EOS anyway? That was always the first thing I uninstalled on all machines
-
Also hp system management homepage (installed on HPE Proliant servers) all ship with PHP.. with no ASLR. There doesn’t appear to be a patch for that, you can use it to surf around flat networks as it drops you as SYSTEM/root.
There’s absolutely shit tons of exploits for PHP2Shell on GitHub and basically none of them actually work to RCE as nobody can figure out ASLR properly.
Which is good, because patching is going to take a long time.
https://php2shell.censys.com/ -
There’s absolutely shit tons of exploits for PHP2Shell on GitHub and basically none of them actually work to RCE as nobody can figure out ASLR properly.
Which is good, because patching is going to take a long time.
https://php2shell.censys.com/If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
-
If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
ASLR supporting PHP exploits are coming, probably next week.. but it’s a really good security control (from decades ago) you should demand your vendors actually enable as it enabled time for orgs paying attention to patch.
The cybersecurity vendor industry itself is essentially negligent when it comes to this stuff. https://infosec.exchange/@catc0n/117487878549556020
-
If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
-
There’s absolutely shit tons of exploits for PHP2Shell on GitHub and basically none of them actually work to RCE as nobody can figure out ASLR properly.
Which is good, because patching is going to take a long time.
https://php2shell.censys.com/@GossiTheDog neat page, though it just assumes versions like 7.4 are unfixed, whereas probably many are using Sury’s PHP which definitely patched it (and I think even 5.6).
There’s probably no better way though to track, so still a useful infographic
-
ASLR supporting PHP exploits are coming, probably next week.. but it’s a really good security control (from decades ago) you should demand your vendors actually enable as it enabled time for orgs paying attention to patch.
The cybersecurity vendor industry itself is essentially negligent when it comes to this stuff. https://infosec.exchange/@catc0n/117487878549556020
@GossiTheDog That toot says there's already a functional ASLR bypass poc out there...?
-
@GossiTheDog neat page, though it just assumes versions like 7.4 are unfixed, whereas probably many are using Sury’s PHP which definitely patched it (and I think even 5.6).
There’s probably no better way though to track, so still a useful infographic
@mig5 yeah if has clarifications for version numbers not being a bulletproof way. But still, orgs historically very bad at patching so it gives a rough indicator picture. Many are just on raw EOL versions, can also see they’re on EOL Redhat etc.
-
@GossiTheDog That toot says there's already a functional ASLR bypass poc out there...?
@christopherkunz there’s one on GitHub but it’s not super functional in reality.. plus people largely haven’t found it yet
it’d need more work to scale. -
@mig5 yeah if has clarifications for version numbers not being a bulletproof way. But still, orgs historically very bad at patching so it gives a rough indicator picture. Many are just on raw EOL versions, can also see they’re on EOL Redhat etc.
@GossiTheDog I can’t believe so many leave expose_php = On !
-
If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
@GossiTheDog Someone never heard of defence in depth?
-
If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
@GossiTheDog Wondering why Colin is having such a strong opinion here. He is quite knowledgeable on good security tradeoffs usually. Purism ?
-
ASLR supporting PHP exploits are coming, probably next week.. but it’s a really good security control (from decades ago) you should demand your vendors actually enable as it enabled time for orgs paying attention to patch.
The cybersecurity vendor industry itself is essentially negligent when it comes to this stuff. https://infosec.exchange/@catc0n/117487878549556020
@GossiTheDog it's like saying
"Why wear a seatbelt, if you have a head on, you'll probably die anyway"
(biting my tongue before I say something rude) -
@GossiTheDog Wondering why Colin is having such a strong opinion here. He is quite knowledgeable on good security tradeoffs usually. Purism ?
It would be easy to dismiss it as security by obscurity, though it's more than that it's akin to the obfuscation of code.
The difference is that the layout of addresses should be random each time it's launched.
But like anything identify the mapping and it's another exercise in lookups.
-
If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
@GossiTheDog@cyberplace.social freebsd destroyed again #lang_en
-
ASLR supporting PHP exploits are coming, probably next week.. but it’s a really good security control (from decades ago) you should demand your vendors actually enable as it enabled time for orgs paying attention to patch.
The cybersecurity vendor industry itself is essentially negligent when it comes to this stuff. https://infosec.exchange/@catc0n/117487878549556020
@GossiTheDog what is #aslr #php
-
If you’re wondering why your million dollar cybersecurity vendor appliances don’t have ASLR enabled.
@GossiTheDog
It's always such a surprise when someone you respect has a dumb take... But then I remember that there are likely so many dumb takes of mine on the internet
-
ASLR adds work factor for attackers but there are a bunch of ways of breaking it. The Blind ROP attacks, for example, are easy to automate. In practice, it's often possible to leak a pointer.
I really hate the naming because there are two different techniques whose names are the wrong way around. Address Space Randomisation (ASR) was first (I think?) shipped in OpenBSD and randomises each
mmapcall. The layout of the address space is random. Address Space Layout Randomisation came from the Linux PaX project. It gives a deterministic layout but with a random base. This is nice for deployment: ASR suffers from the problem (especially on 32-bit systems) that the random addresses may be sufficiently fragmented that a later memory allocation fails because there isn't a sufficiently large contiguous space, but it works the next program invocation with different layout.With ASR, leaking one pointer lets you determine the addresses of all other memory locations in the same region (shared library, malloc bucket, whatever). With ASRL, leaking one pointer is sufficient to determine the location of everything. It turns out it's really easy to leak one pointer. This is even worse for KASLR because your adversary (userspace) has a rich API surface that was never designed on the assumption that kernel addresses were secret (because the MMU means that you can't use a kernel address, even if you know one) and you just need one.
The thing that's changed here seems to be LLMs. Now, rather then using exploit toolkits the include automatic mitigation bypass steps, script kiddies are just asking Claude to produce an exploit. And Claude is doing what LLMs normally do: produce output that looks correct according to a statistical distribution of text. When used in an 'agentic' model, it keeps trying to do this until it finds one output that actually works in the specific conditions that the agentic loop is set up to test. It turns out it's not just nature that can build a better idiot, Anthropic is competing hard in this domain.
The other dimension in this spectrum is the cost. ASLR is basically free. The kernel complexity is tiny (I think the FreeBSD patches had under a hundred lines of functionality change, most of the code was the extra controls for turning it on and off - you really want to be able to turn it off in debuggers, for example, so that your program runs are deterministic, and ideally you want to be able to capture the random seed and replay it so that your debugger can see the conditions that your fuzzer triggered). It also doesn't change the programmer's abstract machine significantly, so if you remove it in the future it won't break things.
If it adds any work factor to attackers, you may as well turn it on because it will at least prevent the least competent ones. And it's embarrassing if your system can be compromised without any effort.
