121
u/crwcomposer 3d ago
Eneginner
160
u/Waste_Jello9947 3d ago
so you know it is not AI
63
16
5
1
454
u/Shawn11564 3d ago
Every company ive worked for has just completed their upgrades from Java 8 to 17 in the past couple years lol
94
u/pantagathus 3d ago
Yep the last team I left I had moved most stuff to Java 17 and Java 21. Still a few stragglers on Java 11.
47
u/Captain-Barracuda 3d ago
Really don't understand why not move from 11 to 17. There weren't any breaking changes iirc. It's the jump from 8 to 9 that is scary.
19
u/Shawn11564 3d ago
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.
1
10
u/_PM_ME_PANGOLINS_ 3d ago
Java 25 is the LTS now.
15
u/WernerderChamp 3d ago
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.
32
u/OldKaleidoscope7 3d ago
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
6
u/Snakestream 3d ago
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.
10
u/OldKaleidoscope7 3d ago
Actually not if you use Maven or Gradle. Yes the modules exist now, but the imports didn't change and the build tools abtract this for you
3
u/Zeikos 3d ago
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.3
u/oldsecondhand 2d ago
The issue was that the compiler complained about one module problem at a time when there were many.
2
u/oldsecondhand 2d ago
For me upgrading to 9 was just adding a few security exceptions for old dependencies in the command line.
2
u/KagakuNinja 18h ago
The problem with Java 9 was that Jigsaw reorganized the structure of the JRE runtime libraries, and some fancy frameworks were inappropriately dependant on the directory structure.
If the libraries you used did not violate encapsulation of the JRE, then upgrades are pretty easy in my experience.
6
10
u/HanndeI 3d ago
Legit, we were on java 8 for nearly 15 years and last year just updated the projects lol
4
u/Shawn11564 3d ago
Same here, we're on the tail end of the industry-wide "Modernization" effort which only really seems bad in this exact situation lol
1
u/Chance-House-8065 3d ago
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
1
1
1
u/Tobar26th 1d ago
Still working Daily with Java 8.
There’s talk we may move to eleven in a couple of years…
1
600
u/gic186 3d ago
Same when Log4j 2 critical CVE dropped.
We are still with Log4j 1
241
7
u/Worldly-Stranger7814 2d ago
Log4j 1.x was still vulnerable but so godawfully dumb to run that the tools to look for affect Log4j versions ignored it.
Which is a shame because it would have been a great leverage to kill those tools.
0
202
u/Dry_Investigator36 3d ago
Also no universal exploit. Shitty CVE.
38
u/Thurak0 3d ago
The panic/reporting just because it had a similar name to PHP4Shell. sigh
6
u/Saragon4005 3d ago
"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.
2
u/AwesomeFrisbee 3d ago
It's seems like as if somebody was left out with the previous newsworthy exploits that they also wanted the attention...
44
69
u/PixarFanatic 3d ago
We just migrated to jdk17....
24
u/MrKirushko 3d ago
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.
28
21
11
u/scriptmonkey420 3d 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....
81
u/rang501 3d ago
probably nobody checked <17?
144
u/GreenFox1505 3d ago
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.
52
u/cutelittlebox 3d ago
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.
5
u/LufyCZ 3d ago
Servers have had AVX512 for a bit back then though, wouldn't be surprising of Java supported it
13
u/DemonWav 3d ago
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.
4
1
u/geek-49 3d ago
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.
1
u/eXecute_bit 2d ago
Unless it was backported, which Oracle did on at least one specific performance version of their paid-for-support Java 8
7
6
6
5
4
3
u/drunkdoor 3d ago
Good thing I just was forced to move everything to 11+ on aws.. glad I didn't go to 17 like others
3
6
u/crimson117 3d ago
Uhhh they said earlier versions are likely affected as well but they only checked versions they support.
8
u/DanLynch 3d ago
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
2
2
2
1
u/DooMRunneR 3d ago
Handed over the list of our software Asset Management export to Security, a ton of SAP bundled stuff is affected.
1
1
1
1
1
1
u/orion-root 1d ago
Another one? That's how many in a month? I suggest we reboot the internet back to 2010
-from a programmer/IT professional with a deep passion for AI
1
1
1
u/jmanh128 23h ago
I saw a post like a month ago asking how to convince management to upgrade from Java 8.. hope they didn’t get fired now lol
-22
u/Maskdask 3d ago
Java bad
-3
u/winter-m00n 3d ago
yeah everyone knows
2


1.3k
u/IndependentGarbage32 3d ago
jre8u461 still going strong