WEBVTT

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

2
00:00:05.680 --> 00:00:11.920
I'm Belinder. It's Wednesday, the eighteenth of November, twenty twenty-six, and this is the evening edition.

3
00:00:11.920 --> 00:00:18.720
Java4Shell: a decoding flaw that can let strangers run code on Java servers.

4
00:00:18.720 --> 00:00:24.080
Java is the quiet engine under much of what UK organisations run.

5
00:00:24.080 --> 00:00:31.840
On 17 November, Oracle's November Critical Patch Update fixed a flaw in it that researchers have named Java4Shell.

6
00:00:31.840 --> 00:00:38.640
It's tracked as C V E twenty twenty-six, one one four nine three eight, the public reference number every known

7
00:00:38.640 --> 00:00:44.640
flaw gets. Sisa, America's national cyber security agency, urged immediate patching.

8
00:00:44.640 --> 00:00:50.427
The detail matters, because whether you're exposed depends on your processors as much as your software.

9
00:00:50.427 --> 00:00:53.600
So, what actually goes wrong?

10
00:00:53.600 --> 00:00:57.680
Base64 is a way of writing binary data as plain text.

11
00:00:57.680 --> 00:01:03.160
Applications use it constantly, for example to carry login details in web requests.

12
00:01:03.160 --> 00:01:11.040
Java has a fast path for decoding it, hand-written for processors with a feature called A V X five twelve vee-bee-em-eye.

13
00:01:11.040 --> 00:01:17.440
Qualys and Calif, who found the bug, place it in how that code treats the final padded group of characters.

14
00:01:17.440 --> 00:01:22.640
Picture a sorter told to fill a 64-slot tray when only two letters remain.

15
00:01:22.640 --> 00:01:26.800
It sweeps the whole tray and spills onto whatever sits beside it.

16
00:01:26.800 --> 00:01:32.440
Here, a short malformed input writes about 62 bytes past the end of a buffer.

17
00:01:32.440 --> 00:01:35.680
Calif says an attacker needs no credentials.

18
00:01:35.680 --> 00:01:42.960
It reports demonstrating remote code execution, or R C E, running the attacker's own code, on default installs

19
00:01:42.960 --> 00:01:48.400
of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.

20
00:01:48.400 --> 00:01:55.680
So, are you exposed? Three conditions must all hold, according to Rapid7 and Qualys.

21
00:01:55.680 --> 00:01:58.840
First, the runtime must be an affected build.

22
00:01:58.840 --> 00:02:00.840
That's open J D K from 17.

23
00:02:00.840 --> 00:02:09.760
0.6 onward, including 21, 25 and 27, plus Oracle's Java 8 Enterprise Performance Pack.

24
00:02:09.760 --> 00:02:16.560
Second, the processor must be x86-64 with A V X five twelve vee-bee-em-eye.

25
00:02:16.560 --> 00:02:22.320
Qualys says that means Intel Xeon from Ice Lake onward and A M D Zen 4 onward.

26
00:02:22.320 --> 00:02:24.880
arm sixty-four is not affected.

27
00:02:24.880 --> 00:02:31.520
Third, untrusted data must reach the decoder, such as credentials checked before a login completes.

28
00:02:31.520 --> 00:02:36.453
Rapid7 says an affected version alone does not make an application exploitable.

29
00:02:36.453 --> 00:02:41.200
Now, the numbers are disputed, and so is the exploitation picture.

30
00:02:41.200 --> 00:02:45.472
Oracle rates the flaw 8.1 under C V S S v3.

31
00:02:45.472 --> 00:02:50.240
1, the zero-to-ten severity score, citing high attack complexity.

32
00:02:50.240 --> 00:02:55.360
Calif rates it 9.2 under the newer C V S S four point zero.

33
00:02:55.360 --> 00:02:59.760
Rapid7 and Qualys list the fixed Oracle builds as 17.

34
00:02:59.760 --> 00:03:06.912
0.21.1, 21.0.13.1, 25.0.5.

35
00:03:06.912 --> 00:03:13.120
1, 27.0.1.1 and 8u513-perf.

36
00:03:13.120 --> 00:03:15.360
Other vendors use their own build numbers.

37
00:03:15.360 --> 00:03:23.200
As of 17 November, Qualys had seen no public confirmation of exploitation in the wild, and Rapid7 reports none.

38
00:03:23.200 --> 00:03:26.640
But Qualys says not to plan around that.

39
00:03:26.640 --> 00:03:28.880
So, what do you do about it?

40
00:03:28.880 --> 00:03:35.480
Patch, then restart every Java process, because a running J V M keeps the old code.

41
00:03:35.480 --> 00:03:38.880
Check bundled runtimes in products and container images.

42
00:03:38.880 --> 00:03:46.800
If you can't patch, both Rapid7 and Qualys give a J V M setting that switches off the fast Base64 decoder, at

43
00:03:46.800 --> 00:03:53.160
some cost in speed. The Secure by Design lesson is that the riskiest code is often the cleverest.

44
00:03:53.160 --> 00:04:00.000
A performance shortcut, in a path every request touches, parsing data from strangers before they've proved who

45
00:04:00.000 --> 00:04:04.760
they are. For UK organisations, the practical question is inventory.

46
00:04:04.760 --> 00:04:09.320
Do you know which products embed Java, and which processors they run on?

47
00:04:09.320 --> 00:04:12.800
As always, this is opinion, not advice.

48
00:04:12.800 --> 00:04:16.880
That was Decrypted, with me, Belinder.

49
00:04:16.880 --> 00:04:20.160
The written version and every source are linked in the show notes.

50
00:04:20.160 --> 00:04:23.760
Thanks for listening. Stay patched, and stay sceptical.

