Hacker News new | past | comments | ask | show | jobs | submit
Super impressive work by Calif as usual.

The exploit conditions are very specific but there are still going to be a lot of hosts impacted. We at Semgrep published some free detection scripts here: https://github.com/semgrep/detection-scripts/tree/main/CVE-2...

They look for these five conditions:

  * HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].
  * x86-64 JVM on an x86-64 host.
  * Version 17.0.6 or later, not at or above a version listed in FIXED_IN, and no newer than the newest releases checked (see below). Newer versions are [?]: they may carry the fix.
  * The JVM reports avx512_vbmi and avx512bw, and UseAVX >= 3.
  * Base64 intrinsics are on and C2/JVMCI can compile. These turn it off: -XX:-UseBASE64Intrinsics, -XX:DisableIntrinsic=_base64_decodeBlock, -Xint, -XX:TieredStopAtLevel below 4.
The write-up itself matches your version assumption, however it also says:

> According to Oracle, the following Oracle Java SE versions are vulnerable: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3. We thank Oracle for providing this information ahead of publication time.

So according to Oracle at least, JRE8 versions are affected as well.

25.0.5.0.3 is the latest on the 25 version [0]. Does that mean no patch is available?

[0] https://www.oracle.com/java/technologies/javase/jdk25-archiv...

That's the archive page for older downloads. The main download page [1] reports the latest version as 25.0.5.1.

[1] https://www.oracle.com/java/technologies/downloads/#java25

Ofc they needed 5 version numbers.
Wow, yeah. Why do they need 5 version numbers!?
loading story #50542298
Seems like it's only a specific "performance pack" version of JRE8 that backported these changes that is vulnerable. Standard JRE8/11 is fine.
loading story #50547373
one note: it means -XX:-UseBASE64Intrinsics OR XX:DisableIntrinsic=_base64_decodeBlock OR -Xint OR -XX:TieredStopAtLevel below 4 (-XX:TieredStopAtLevel=3 and so on)
Wouldn't it be prudent for someone to patch even if they aren't running their code on an AVX512 system right this moment? They could be running on one.. next moment.
Sure, but I think it brings it down from "patch immediately" severity, to just "bump the JDK with next service deploy" severity.

Or, do running machines often have their CPU changed from under them without much notice?

Depends on the company and deployment method. As Ops person, I generally don't think much about rolling out different Kubernetes Nodes and what SKU I select. So yes, you could be running on one node type today and tomorrow I upgrade the nodes under you.
loading story #50539846
loading story #50541993
> Or, do running machines often have their CPU changed from under them without much notice?

I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.

loading story #50540131
loading story #50540529
This looks like Claudese - may be kind to write such things yourself if you intend for humans to read them. (For example, “ HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].” — I tried parsing at least five times before realizing you’re asking me to decipher LLM talk)
I understood it on first read, anyone that is comfortable with Java ecosystem easily understands the differences between those JVM implementations.

Here are three more, PTC, Aicas, and ART (even if it runs DEX instead, and only the core language is supported).

I still don't understand what's meant with Azul. Is it affected or not? What is it never?
Azul Core definitely is - it uses upstream HotSpot.

Azul Platform Prime (formerly Zing) may or may not be depending on whether they touched the base64 intrinsic. Since it is closed-source there is no way to verify via code, which is how our research team investigates ecosystem events like this.

What's with this weird tendency to think everything you don't immediately understand is LLM? It's okay to not understand things. Have you worked with Java at all? Why do you expect to make sense of those technologies if not?

I've done Android development and there's nothing wrong with the way it's phrased. All of that is high signal information.

I've been working with Java for 30 years. The whole thing is phrased oddly and it has nothing to do with the specific technologies.
loading story #50544836
loading story #50547737
Calif is an OpenAI funded shop..
Oracle owns Java and Oracle is "OpenAI funded" in the sense that Oracle's data center buildouts are being done using OpenAI as a consumer.

The circular financing continues!

But seriously, the funding here doesn't matter any more than Project Zero's funding comes from Google. Big companies are trying to improve security for the common software substrates of our industries / governments.

> Big companies are trying to improve security for the common software substrates of our industries / governments.

"improve security" in the same way that my dad used to beat us

Security by obscurity has never been a good idea, especially in the tech industry and even less so since the advent of LLMs
Native Image is also unaffected without `-march=native` which is not a default.
I don’t understand what you mean. Could you remove the triple negative to clarify?