Repository navigation
Detect Oracle Java 8 Enterprise Performance Pack (EPP) - #12
Merged
Merged
Conversation
EPP runs a JDK 17 HotSpot JVM under the Java 8 class library, so a 1.8.0_NNN runtime can carry the vulnerable decodeBlock stub. The scripts compared only java.version against 17.0.6 and reported EPP as not impacted. When a Java 8 build carries "-perf", check the JDK 17 JVM version from the perf build string instead (java.vm.version on hosts; package name, version or image name in the cloud scripts). If that version cannot be read, report [?] rather than OK. Fixes #7 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #7.
Oracle Java 8 Enterprise Performance Pack runs a JDK 17 HotSpot JVM under the Java 8 class library. Its runtime reports
1.8.0_NNN, so every detector ruled it out as older than 17.0.6. The JVM is what generates and installs the Base64decodeBlockintrinsic, so the JDK 17 JVM version is what decides whether EPP is impacted.Changes
linux/detect-jdk-8392044.sh,windows/Detect-Jdk8392044.ps1): whenjava.versionis1.xand the build carriesperf, read the JDK 17 version fromjava.vm.version. Oracle's documented example is17.0.4+1-perf-4711. If that is missing, fall back to anyperfline in thejava -versionoutput. The usual 17.0.6,FIXED_INandCHECKED_THROUGHchecks then apply. If the JVM version can't be read, the result is[?].cloud/detect-jdk-8392044-{aws,gcp}.sh): newver_eppandver_pkghelpers, identical in both scripts and added to the drift test. They search package name and version, or the image name, for an EPP build and its JVM version. Inventory usually doesn't include the JVM version, so EPP there normally reports[?]"JVM version not visible".Testing
FIXED_INis OK, plain Oracle 8 is OK). Run in a linux/amd64 container.-S warningclean.javaneeds Windowscsc.🤖 Generated with Claude Code