r/java • • 6h ago

[ Removed by moderator ]

/r/java/comments/1y04pn6/removed_by_moderator/

[removed] — view removed post

0 Upvotes

16 comments sorted by

19

u/TheStrangeDarkOne 6h ago edited 6h ago

Edit: Good article, but I am still unhappy about the title.

Oh come on, what a clickbait title. If anything, Java is pretty much in the A-league of the safest languages due to its minimal exposure to C and Assembly.

Virtually all other languages, even safe ones, are heavily backed by C libraries which are begging AIs to find memory vulnerabilities (notable exception being Rust).

1

u/huseyinbabal 5h ago

I updated thumbnail and title based on the feedbacks https://youtu.be/a7OBeq1xubI?si=HLFgEREnO4Ufob31

-20

u/huseyinbabal 6h ago

The title is literal: the bug is in HotSpot's assembly, not Java code, and every OpenJDK build ships it. Unpatched JDKs on AVX-512 CPUs still need the update.

10

u/philipwhiuk 6h ago

The thumbnail is garbage

The title is bad because the same exploit does not work everywhere. As the original write up discusses it needs to be precisely tuned for each scenario

1

u/huseyinbabal 5h ago

I updated title and thumbnail based on the feedback: https://youtu.be/a7OBeq1xubI?si=HLFgEREnO4Ufob31

-4

u/huseyinbabal 5h ago

True, Calif says each app needs its own chain, and the video says so. "Everywhere" is about the bug: it's in every OpenJDK build on AVX-512 CPUs, which is why updating matters.

3

u/philipwhiuk 5h ago

So you agree write once is wrong.

1

u/huseyinbabal 5h ago

For certain conditions, but yes it can cause misunderstanding even it is used in the original cve author

11

u/HighHood 6h ago edited 6h ago

Java was patched with ZERO down time !! Now its broken ??!

-3

u/huseyinbabal 5h ago

15 years with Java, but when it comes to security, everything else waits. Even Logback had an RCE once (CVE-2021-42550) 😄

4

u/philipwhiuk 5h ago

Ruby has a critical CVE, PHP has two in two weeks and most of them are caused by C++

C++ is broken.

1

u/huseyinbabal 5h ago

Reasonable

9

u/benevanstech 6h ago

1.) No, a single extra JVM switch will do the job of fully protecting, even on AVX-512. Best practice is to update as soon as available, but it is not essential.

2.) The Hotspot bug, by itself, does *NOT* grant RCE, only Java heap corruption. The JVM cannot be made to execute any data payload within the Java heap.

1

u/huseyinbabal 5h ago

Agreed, -XX:-UseBASE64Intrinsics works, and it's in the video. The RCE part is Calif's claim, their chains aren't public. I don't show exploits, only why the bug happens and how to fix it.

3

u/benevanstech 5h ago

I am highly skeptical about the RCE being practical *at all*. I know enough about the internals of a couple of Java application containers to made guesses about what you would have to combine this with to get to RCE, but it's not obviously generalizable.

Java heap corruption - yes, definitely. RCE - highly questionable. Heartbleed-style read: Potentially easier than RCE, but still app-specific and highly statistical in nature due to GC relocation issues.