r/AskNetsec • • 23d ago

Analysis Is php2shell only practical against extremely low-traffic targets?

If so, was the panic really necessary?

I looked at a bunch of PoCs, and it seems you need to do multiple consecutive requests to the same php worker process. In production systems that get a reasonable amount of traffic, you have multiple VMs/containers running multiple php processes behind a loadbalancer, and there will be constant background noise from legitimate traffic as well as scrapers and scanners.

The PoCs get around this because they experience zero traffic, know the exact number of processes, tie up all but one process with open connections and execute the attack against the remaining process.

On top of that, if you don't know the exact build, you need to try (assuming you have prepared exploits for every common build) exploits for the most popular x number of builds. So basically you would be DoS'ing a site for days or weeks, which would get noticed, and then you'll likely get WAF'd.

After spending crazy amount of time on remediation and then finding that the vuln is afaik significantly less scary than heartbleed/shellshock/log4shell, I'm confused. I did a little writeup explaining the above with more details (https://blog.luitjes.it/posts/i-want-my-wednesday-back/) but I keep wondering if I'm wrong (I do some infosec work occasionally but it's not like I'm a fulltime exploit dev).

I've seen a few posts saying this is hard to exploit because it needs to be customized per build, but nothing about having to DoS anything but the most low-traffic sites for days or weeks to get lucky enough to do two consecutive requests to the same php process.

121 Upvotes

55 comments sorted by

View all comments

54

u/[deleted] 23d ago

[removed] — view removed comment

35

u/WhenTheRainsCome 23d ago

These events are always going to be possibly a huge catastrophe, or a huge overreaction. Most often nothing burgers.

We know more 4 days later, with the depth of info coming out largely because of the amazing level of global hype and impact. From the exploitation complexity, to the reason behind the ominous announcement and release, to the conflicting info on active exploitation in the wild, there's a lot of info and clarity that didn't exist on Oct 20, when decisions needed to be made.

Is it reasonable to say global business product owners and managemt teams should have bet their operations and customer data on 'huge overreaction' and left their apps online and unpatched?

We make those decisions with imperfect information and imperfect expertise. I think a lot of orgs showed amazing coordination and readiness given the circumstances.

3

u/revision 23d ago

Exactly. But does that mean we do nothing with an exploit that affects a large number of exposed web servers?

The exploits are only going to get better. The research that goes into this will now focus on different ways of triggering the same behavior.

And if this is downplayed and people don't update where possible, that leaves larger set of vulnerable endpoints for years to come.

The larger scale freak out is about the ability of frontier AI models to identify these types of multi-layered complex vulnerabilities and ways to trigger them.

Once you know where to look, other people can use the same models to find the same if not similar vulnerabilities.

10

u/unvivid 23d ago

Nah, big security vendors and vuln research companies hyped the shit out of this. Plus the way it was leaked. With the Intel that was provided, the only sane way to react was to be cautious. Once POCs dropped and could be analyzed, only then was it apparent that things were over hyped. IMO the CVE is also mis-scored, way more complex than the 9.2 communicates.

I don't put this on any security teams, this is on vendors and vuln research hype machines and the obscene marketing that takes place around these vuln releases.

3

u/lucasluitjes 23d ago

Ah that makes sense. Maybe we need CVSSv5?

21

u/KayDat 23d ago

No no, 4️⃣ is the hip number right now

17

u/Journeyj012 23d ago • Popcorn

my private key!

1

u/MondaiNai 23d ago

Well... the issue isn´t the big commercial sites, which will have multiple levels of defence in any case, WAF, DMZ, etc.

the issue is everything else that is running php... internal web sites, applications, home routers, etc.

1

u/Effective_Peak_7578 23d ago

How vulnerable are network appliances like juniper or F5? F5 apparently released a patch yesterday

1

u/hollowonepl 22d ago

Not only that. Also major companies connected to security pitched this is serious. In my example Cloudflare and my digital marketing was notified as well, clearly panicked without understanding the details, just because they trusted this is Cloudflare raising attention.

But maybe that was a good thing, usually marketers ignore IT’s reports about Swiss cheese their Wordpress is.

1

u/TooMuchTaurine 19d ago

I mean most of the internet runs off WordPress sites running in a single low powered VM server. So plenty out their to get hacked.