Skip to content

Detect Oracle Java 8 Enterprise Performance Pack (EPP) - #12

Merged
kurt-r2c merged 1 commit into
mainfrom
kb/jdk8-epp-detection
Nov 18, 2026
Merged

kurt-r2c merged 1 commit into
mainfrom
kb/jdk8-epp-detection

Conversation

@kurt-r2c

Copy link
Copy Markdown
Collaborator

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 Base64 decodeBlock intrinsic, so the JDK 17 JVM version is what decides whether EPP is impacted.

Changes

  • Host scripts (linux/detect-jdk-8392044.sh, windows/Detect-Jdk8392044.ps1): when java.version is 1.x and the build carries perf, read the JDK 17 version from java.vm.version. Oracle's documented example is 17.0.4+1-perf-4711. If that is missing, fall back to any perf line in the java -version output. The usual 17.0.6, FIXED_IN and CHECKED_THROUGH checks then apply. If the JVM version can't be read, the result is [?].
  • Cloud scripts (cloud/detect-jdk-8392044-{aws,gcp}.sh): new ver_epp and ver_pkg helpers, 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".
  • README: an EPP paragraph under "What counts as impacted".

Testing

  • Linux suite: 6 new EPP cases (EPP on 17.0.17 is impacted, on 17.0.4 is OK, newer than checked is unknown, unreadable JVM version is unknown, fixed via FIXED_IN is OK, plain Oracle 8 is OK). Run in a linux/amd64 container.
  • AWS suite 71/71 and GCP suite 51/51, including new EPP inventory fixtures and the AWS/GCP drift check.
  • shellcheck -S warning clean.
  • The same 6 cases are added to the Windows suite. They run in CI only, because the fake java needs Windows csc.

🤖 Generated with Claude Code

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>

@diptendur2c diptendur2c left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK!

@kurt-r2c
kurt-r2c merged commit ef9d8d3 into main Nov 18, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CVE-2026-114938 and Oracle Java 8 EPP

2 participants