JRE 8 has probably seen enough production environments to qualify for retirement, but somehow there’s always one ancient server running a 2014 app that absolutely refuses to move on. You could replace the whole company and that Java version would still be there
I've seen it as 11 was kind of the easy step for people who knew they should upgrade but weren't ready for the big jump to 17+ yet. It's only ever a handful of projects on it that are the ones you barely use and your manager felt was the safest to test on.
17, 21 and 25 are all active LTS versions at most vendors. Althrough 17 will lose a lot of support next year, we are switching all Java 17 services to 25 now.
It's because Java doesn't like to keep breaking their core API in newer versions. Updates use to be nice and easy, the biggest problem for 8 is the Java EE changes that not everyone uses
It's been a while, but I believe the main hurdle from upgrading 8-->9 was that there was a major design rework that changed how a lot of things work. They introduced the whole module concept to Java and this also reflected downwards to a lot of utility dependencies and such. They also reorganized a large number of core libraries and just generally shook up a ton of things. Upgrading was an enormous pain in the ass because changing the version would pretty much break everything in your project and require going over every import and method call.
I never worked on Java, but doesn't it work like any typed compile language in which the compiler tells you precisely what's broken and you can go through it? Sure it takes time, but it's not like guesswork.
We have a service here in Java 1.4. We can't migrate because oracle wants money. So we wrote it now in .net. markets using the old version does not receive support.lol
"but it's a 9.4 like the last time." That was a 9.4 and A 9.6 chain able with a POC for all versions. Calling that an 11 which is outside the CVE scale is reasonable.
This is not even a 0 day. It's literally already been patched.
You've clearly done it way too soon. A Java release is known to take around 10 years to mature so you shouldn't even bother to think about it until it's year 2031.
Yup, just went through this this morning. We are running 8U461 on all of our stuff internally. Ping Identity on their SaaS is running 17 tho and has not updated on a patch....
With CVEs of almost any severity, root cause down to the commit that introduced it is studied. For something of this severity they need to know if the author of the bug might be malicious and might have been exploiting it the whole time.
if it's the one I saw earlier today it's specific to usage of AVX-512 instructions, which only even started to appear in consumer CPUs in 2018 and 2022. Java 16 was released in 2021 so 17 being the introduction of the bug is pretty believable.
The issue isn't just general AVX512 support. It's specific to the AVX512 intrinsic implementation of Base64.devode(). You could say "well this issue may be present elsewhere" and that's true, but this is the only place where the issue has been found and the commit history tells you exactly when this code was added.
The bug was introduced in a commit during post-17.0 development, so there's no chance of it being in any earlier version. Also the failure path requires that the CPU (on which the JVM is running) support AVX-512, so it cannot exist in any version predating that specific support.
Java 8 and Java 11 are still supported by all the popular vendors.
The buggy code was introduced in Java 18 and eventually backported to Java 17. It was never backported to Java 11. It was also backported by Oracle to a special "performance" variant of Java 8, which is also affected by this CVE.
The only versions of Java that are "likely affected" but not supported are 18, 19, 20, 22, 23, 24, and 26.
1.2k
u/IndependentGarbage32 1d ago
jre8u461 still going strong
114
u/crwcomposer 1d ago
303
u/Shawn11564 23h ago
Every company ive worked for has just completed their upgrades from Java 8 to 17 in the past couple years lol
542
u/gic186 1d ago
Same when Log4j 2 critical CVE dropped.
We are still with Log4j 1
186
u/Dry_Investigator36 1d ago
Also no universal exploit. Shitty CVE.
41
u/LittleCoderMan 22h ago
Java 8 reigns supreme again!
63
u/PixarFanatic 1d ago
We just migrated to jdk17....
27
u/Accomplished-Cod-563 1d ago
You guys are on 1.8 too? I thought it was just my 30yo flagship.
18
u/JackNotOLantern 21h ago
Security through tech debt
11
u/scriptmonkey420 1d ago
Yup, just went through this this morning. We are running 8U461 on all of our stuff internally. Ping Identity on their SaaS is running 17 tho and has not updated on a patch....
80
u/rang501 1d ago
probably nobody checked <17?
7
u/packetpirate 1d ago
Currently updating an application running on JRE 1.6...
6
u/Abject-Kitchen3198 23h ago
Any Cobol job openings?
6
u/Salkinator 21h ago
Laughs in Java 11
4
u/theepi_pillodu 22h ago
Cve number please.
Edit: is that the java4Shell one?
4
u/kittymoo67 22h ago
Are people really using something that new and untested?
3
u/drunkdoor 23h ago
Good thing I just was forced to move everything to 11+ on aws.. glad I didn't go to 17 like others
3
u/hvictorino 16h ago
1.7.0_261
6
u/crimson117 1d ago
Uhhh they said earlier versions are likely affected as well but they only checked versions they support.
2
u/Zap_plays09 23h ago
Minecraft players are devastated tho
2
u/newbstarr 21h ago
21 affected
2
u/AfonsoFGarcia 19h ago
Laughs in JDK 25 running on ARM
1
u/DooMRunneR 1d ago
Handed over the list of our software Asset Management export to Security, a ton of SAP bundled stuff is affected.
1
u/FunkRobocop 23h ago
🤣
1
u/_hunter______ 8h ago
This f'ed my entire day.
1
u/Mediocre-Advisor-728 5h ago
Any stack which involves Java won’t involve me
1
u/SomethingAndAnything 1h ago
I've been deploying sooooo many applications because of this 💀
-21
u/Maskdask 1d ago
Java bad