Latest / Decrypted: The UK Cyber Briefing / PHP's flaws have now taken government services offline, and exploitation began before the patch
Transcript
- 0:03This is Decrypted. Thursday, the twenty-second of October, twenty twenty-six.
- 0:09This is the evening edition.
- 0:11P H P's flaws have now taken government services offline, and exploitation began before the patch.
- 0:20Yesterday's P H P story has gone from advisory to outage.
- 0:26Ministers told the Lords on Thursday that 32 government services were unavailable and four were partially una
- 0:34vailable. That was largely down to precautionary measures while updates and mitigations were applied.
- 0:41Downing Street said that doesn't mean the systems were hacked, and that no large public-facing critical servi
- 0:48ces were affected. So, what's actually new since the advisory?
- 0:54The N C S C, the National Cyber Security Centre, part of G C H Q, published its alert on 21 October.
- 1:04It covers C V E twenty twenty-six, one zero nine six one eight and C V E twenty twenty-six, one zero nine six
- 1:15one nine, the public reference numbers these two vulnerabilities have been given.
- 1:20It says organisations using any version of P H P are affected.
- 1:25Its advice is plain. Update to the latest version.
- 1:29And if you can't apply mitigations quickly, consider taking the system offline until you can.
- 1:35Government appears to have done exactly that.
- 1:38The fresh evidence is about exploitation.
- 1:41Help Net Security reports that Amazon's honeypot recorded an exploitation attempt on 17 October, four days be
- 1:49fore public disclosure. How the attacker got the details is still unknown.
- 1:54L B C reports that Cloudflare's Matthew Prince saw thousands of attempts in the ten hours before the announce
- 2:01ment. Now, how do these flaws actually work?
- 2:06Picture a restaurant kitchen where a torn-up order leaves a pan on the hob, and the next order is cooked on
- 2:13top of it. BleepingComputer explains that P H P can leave its memory in a corrupted state when a request ends
- 2:20abnormally, and both flaws grow from that.
- 2:23One abuses out-of-memory handling.
- 2:26The other leaves stale internal state behind after the memory has been freed.
- 2:31Either can give an attacker remote code execution, or R C E, meaning they run their own commands with the web
- 2:38server's privileges. The P H P team says the risk is highest with mod_php, where one unauthenticated request
- 2:47can trigger the attack before any application code runs.
- 2:51That's why updating your content management system changes nothing.
- 2:55The fault sits underneath, in the language runtime.
- 2:58So, what does a defender actually see?
- 3:03Very little. The request looks like ordinary web traffic, and the damage happens before your application log
- 3:09s anything. Cloudflare says sites behind it have an initial set of waff rules, a web application firewall bein
- 3:17g a filter in front of a website.
- 3:18But P H P's own advice is that interim settings such as memory_limit=-1 don't fully protect you.
- 3:26Updating is the only safe choice.
- 3:30The fixed versions are 8.5.
- 3:3312, 8.4.27, 8.3.36 and 8.2.
- 3:4035, with minimal backports for 7.
- 3:434, 8.0 and 8.1. And what's the Secure by Design lesson here?
- 3:48It's dependency you can't see.
- 3:51Many UK organisations can't say how many P H P installations they run, because P H P hides inside appliances,
- 3:59intranets and supplier portals.
- 4:01Secure by Design means holding that inventory before the alert arrives.
- 4:06It also means having a rehearsed way to take a service down cleanly, which is what the government's Thursday
- 4:12amounted to. It costs a spreadsheet and an afternoon.
- 4:16Amazon's attempt four days before disclosure carries a second lesson.
- 4:20The quiet period before a patch isn't safe, so assume exploitation can begin before your supplier's email arr
- 4:28ives. As always, this is opinion, not advice.
- 4:32That was Decrypted. The written version and every source are linked in the show notes.
- 4:38Thanks for listening.