Repository navigation
fix(security): block disclosed eMudhra chains in JVM connector and CLI images - #102
imperfect-fourth wants to merge 3 commits into
Conversation
1.24 ships ca-certificates 2026.2.92, which already removes the other emSign roots. Replace the 16-fingerprint blocked.certs list with an OS-level blocklist of the remaining G1 anchor (update-ca-trust regenerates the JVM cacerts). No-op once RHEL drops G1.
…1 blocklist Red Hat has not yet shipped a fixed java-21-openjdk for UBI 9 (RHSB-2026-018), so the snowflake, mysql, oracle, trino and CLI images keep the ubi9/openjdk-21 1.24 bases and set JDK_JAVA_OPTIONS=-XX:-UseBASE64Intrinsics, Red Hat's documented temporary workaround. This is a mitigation, not a fixed JDK; remove it once a fixed RPM is in the base image. Also ports #102's emSign Root CA - G1 trust-store blocklist, builds the arch-independent Gradle stage on the build platform, and stops the NDC tests workflow re-installing the MySQL client (the runner already has it; the reinstall broke on a mysql-server postinst).
|
Superseded by #103 (merged in 7606ff9). Closing this. #103 carries this PR's emSign Root CA - G1 blocklist in the runtime stage of the snowflake, mysql, oracle and trino connector dockerfiles and Not covered by #103: As noted here, none of this reaches running connectors until new |
Mitigates the eMudhra distrust for all
ndc-jvm-*connector images andndc-jvm-cli.registry.access.redhat.com/ubi9/openjdk-21:1.23to:1.24(floating, latest 1.24.x). 1.24 shipsca-certificates2026.2.92, which removes emSign ECC Root CA - C3/G3 and emSign Root CA - C1.emSign Root CA - G1is still a trusted server-auth anchor in 1.24, so the final stage exports it into/etc/pki/ca-trust/source/blocklist/and runsupdate-ca-trust extract(the JDKcacertsis a symlink to/etc/pki/java/cacerts, so OS and JVM are both covered). The build asserts G1 is absent from the JVM store.Not released: needs new
<db>/v*tags and redeploys to reach running connectors.