WEBVTT

1
00:00:03.200 --> 00:00:05.680
Good morning, and welcome to Decrypted.

2
00:00:05.680 --> 00:00:11.787
I'm Belinder. It's Friday, the twentieth of November, twenty twenty-six, and this is the morning edition.

3
00:00:11.787 --> 00:00:18.480
P H P's seven critical flaws land four weeks after P H P two shell.

4
00:00:18.480 --> 00:00:25.440
P H P, the scripting language behind a large share of the web, shipped fixes on Thursday for seven flaws it

5
00:00:25.440 --> 00:00:32.560
rates critical. Each can lead to remote code execution, or R C E, which means a stranger running their own code

6
00:00:32.560 --> 00:00:38.440
on your server. security week's reporting gives no sign that these seven are being exploited yet.

7
00:00:38.440 --> 00:00:45.360
But they arrive four weeks after P H P two shell, a pair of flaws that attackers were probing before any patch

8
00:00:45.360 --> 00:00:49.307
existed. Several of the new ones touch the same machinery.

9
00:00:49.307 --> 00:00:57.520
So if you run a website, intranet or customer portal on P H P, this is a patching week, not a patching quarter.

10
00:00:57.520 --> 00:01:00.720
So, what did P H P actually fix?

11
00:01:00.720 --> 00:01:06.960
P H P said the critical issues "require either non-default configuration or uncommon setups".

12
00:01:06.960 --> 00:01:09.920
That's reassuring, but it's not a pass.

13
00:01:09.920 --> 00:01:14.640
Several concern sessions, the code that remembers who you are between page loads.

14
00:01:14.640 --> 00:01:22.000
In one, data is written in one format and read back in another, so a decoder can mistake part of it for instructions.

15
00:01:22.000 --> 00:01:27.280
Picture a post room where a parcel labelled as a letter is opened by the wrong clerk.

16
00:01:27.280 --> 00:01:33.160
The one to read twice sits in P H P-F P M, the process manager many hosts use.

17
00:01:33.160 --> 00:01:36.880
Unread bytes of a request can be treated as a second request.

18
00:01:36.880 --> 00:01:41.360
That slips past front-end routing and runs P H P code as the worker.

19
00:01:41.360 --> 00:01:44.640
security week says an attacker needs no login.

20
00:01:44.640 --> 00:01:46.464
Full fixes are in P H P 8.

21
00:01:46.464 --> 00:01:52.400
6.0 and 8.5.13. Most issues are also fixed in 8.

22
00:01:52.400 --> 00:01:58.784
4.28, 8.3.37 and 8.2.36. P H P says 8.

23
00:01:58.784 --> 00:02:03.760
2 reaches end of life on 31 December 2026.

24
00:02:03.760 --> 00:02:06.400
Why does the October episode matter here?

25
00:02:06.400 --> 00:02:12.840
According to security week, Amazon saw the first P H P two shell exploitation on 17 October.

26
00:02:12.840 --> 00:02:18.680
That was four days before the 21 October patches, while the flaws were still under embargo.

27
00:02:18.680 --> 00:02:24.360
Cloudflare's chief executive reported thousands of attempts in the ten hours before the announcement, rising

28
00:02:24.360 --> 00:02:30.840
to millions later. watch-tower said none of the public proof-of-concept code it saw achieved code execution,

29
00:02:30.840 --> 00:02:32.587
so much of that was noise.

30
00:02:32.587 --> 00:02:34.693
But the lesson is about time.

31
00:02:34.693 --> 00:02:38.760
The gap between disclosed and attacked is measured in hours.

32
00:02:38.760 --> 00:02:41.880
So what should you take from this on Secure by Design?

33
00:02:41.880 --> 00:02:44.400
Three decisions limit the damage.

34
00:02:44.400 --> 00:02:51.440
First, don't rebuild objects from data your own code didn't produce, because two of the seven turn on exactly

35
00:02:51.440 --> 00:02:59.440
that. Second, run each site as its own low-privilege user, so one flaw doesn't hand over every secret on the server.

36
00:02:59.440 --> 00:03:04.920
Third, keep an inventory with an owner for every P H P version in service.

37
00:03:04.920 --> 00:03:11.680
P H P 8.1 and older get no project updates, so a forgotten legacy site is the likeliest victim.

38
00:03:11.680 --> 00:03:18.120
Several of the seven also need help from the application itself, such as a suitable chain of code to abuse.

39
00:03:18.120 --> 00:03:21.440
The cost is a day of listing and a week of upgrades.

40
00:03:21.440 --> 00:03:27.360
Compare that with an incident review, a regulator's questions and customers asking what you knew.

41
00:03:27.360 --> 00:03:30.907
As always, this is opinion, not advice.

42
00:03:30.907 --> 00:03:35.200
That was Decrypted, with me, Belinder.

43
00:03:35.200 --> 00:03:38.720
The written version and every source are linked in the show notes.

44
00:03:38.720 --> 00:03:42.240
Thanks for listening. Stay patched, and stay sceptical.

