Skip to content

Update Nexus to 3.94.3 to remove trust in eMudhra CAs - #5279

Merged
Jay W (JayDoubleu) merged 1 commit into
microsoft:mainfrom
JayDoubleu:fix/nexus-3.94.3-emudhra
Oct 28, 2026
Merged

Jay W (JayDoubleu) merged 1 commit into
microsoft:mainfrom
JayDoubleu:fix/nexus-3.94.3-emudhra

Conversation

@JayDoubleu

@JayDoubleu Jay W (JayDoubleu) commented Oct 28, 2026 •

Copy link
Copy Markdown
Collaborator

Resolves #5276

What is being addressed

The JVM in Nexus 3.94.0 trusts certificates from 8 eMudhra intermediate CAs. The private keys of these CAs are compromised (Sonatype advisory). The CA generated the keys incorrectly, and anyone can recover them from the public certificates (incident page).

On 28 October 2026, Sonatype released Nexus 3.94.3. The advisory lists 3.94.3 as a fixed version. The container images of 3.94.3 do not trust the compromised CAs.

This PR stays on the 3.94 line. It does not add the required base telemetry of Nexus 3.97 and later, and it does not need action from an operator. #5271 covers the upgrade to the latest Nexus version and its telemetry. PR #5278 does that upgrade.

How is this addressed

  • templates/shared_services/sonatype-nexus-vm/porter.yaml: change the image tag from 3.94.0 to 3.94.3, and the bundle version from 3.11.2 to 3.11.3.
  • CHANGELOG.md: add a BUG FIXES entry.

The bundle version is a patch version, because the upgrade does not need action from an operator. On an upgrade, the existing run command imports the new image and restarts the Nexus container on the same VM.

The Docker Hub tag 3.94.3 has the digest sha256:0ac09d5b2a75f27f129859beff3bd196a410a5a7ebd7f7d7013359ebc97ed327. The tag 3.94.3-alpine has the same digest.

Test results

JVM TLS test

The test runs a small Java client with the JVM and the default trust store of each image. The client connects to pypi.org, files.pythonhosted.org and the 14 test hosts of the incident page.

Hosts Nexus 3.94.0 Nexus 3.94.3
pypi.org and files.pythonhosted.org Connects Connects
6 hosts with a direct eMudhra chain, for example dv-g3b-emudhra.we-have-a-problem.com Connects Rejects
dv-g3b-noct-emudhra.we-have-a-problem.com, with a certificate that is not in a CT log Connects Rejects
7 hosts with the Sectigo cross-sign, for example dv-g3b-aaa-emudhra.we-have-a-problem.com Rejects Rejects

Each rejection is SunCertPathBuilderException: unable to find valid certification path to requested target.

Image Java Alpine
3.94.0 21.0.11 3.24.1
3.94.3 21.0.12 3.24.3

Sonatype chain check

Sonatype added EmudhraChainCheck.java to sonatype/docker-nexus3 in PR 325. It tests the JVM against the 12 chains of the advisory. It also tests a re-encoded copy of each intermediate, so it has 24 cases. A re-encoded copy has different bytes but a valid signature. A block list of intermediate fingerprints does not stop it, but a removed root does.

Image Result
3.94.0 Trusts 12 of 24 cases
3.94.3 This JRE rejects all 24 compromised eMudhra chains and re-encoded variants

Why one eMudhra root is still in the trust store

The JVM cacerts and the OS bundle /etc/ssl/certs/ca-certificates.crt of the 3.94.3 image still contain one eMudhra root. This root is emSign Root CA - G1 (SHA-256 40:F6:AF:03:46:A9:9A:A1:CD:1D:55:5A:4E:9C:CE:62:C7:F9:63:46:03:EE:40:66:15:83:3D:C8:C8:D0:03:67).

The compromised keys belong to 8 intermediate CAs, not to all eMudhra CAs. The fix of Sonatype (PR 324 and PR 325 on sonatype/docker-nexus3) blocks the 4 roots that issued these intermediates:

  • emSign Root TLS CA - G3
  • emSign Root CS CA - G3
  • emSign ECC Root CA - G3
  • AAA Certificate Services (the Sectigo cross-sign)

emSign Root CA - G1 is not in this list. The tests found these facts:

  • revoked-intermediates.sha256 lists 16 certificates. These are the 8 intermediates, each with two issuers. Each issuer is a G3 root or AAA Certificate Services. G1 is not the issuer of any of them.
  • In the 3.94.3 image, blocked.certs of the JVM contains all 16 intermediate fingerprints and all 4 root fingerprints.
  • The 4 roots are not in cacerts and not in the OS bundle.
  • The JVM rejects all 14 advisory test hosts and all 24 cases of the chain check.

These results apply to the published chains of the 8 compromised intermediates. The tests do not prove anything about other CAs under G1. It is possible that Sonatype, the JDK or the Alpine ca-certificates package will remove or change G1 in the future. If that happens, a later image update will include the change.

Local upgrade test (Podman)

  1. Nexus 3.94.0 started on a new data volume.
  2. The test accepted the EULA (HTTP 204), created a raw hosted repository (HTTP 201) and uploaded a file (HTTP 201).
  3. Nexus 3.94.3 started on the same volume after 25 seconds. The server header shows Nexus/3.94.3-02 (COMMUNITY).
  4. The EULA was still accepted, the repository was still present, and Nexus returned the file content with HTTP 200.

After the upgrade, the status check showed two warnings:

  • Default Secret Encryption Key: this warning also shows on 3.94.0, because the test container has no encryption key.
  • Scheduler: "Missing triggers were auto-recovered for 1 task". A restart of 3.94.0 on its own data gives the same warning, so the upgrade does not cause it.

The packages that Nexus serves are a separate issue

This PR changes only the trust store of Nexus. It does not change the packages that Nexus serves. Many packages contain their own list of trusted CAs, for example certifi and pip on PyPI. These packages continue to trust the compromised CAs until workspaces install fixed versions.

Shared service tests in Azure

/test-shared-services accept_nexus_eula ran in run 40670903808. The run deployed a new Nexus with bundle 3.11.3 and the image 3.94.3.

Job Result
Run E2E Tests (Smoke) Passed
Run E2E Tests (nexus) Passed
Run E2E Tests (other) 3 passed, 1 failed

The one failure was in the Airlock notifier test, which this PR does not change. One poll of the delete operation got HTTP 500 from the API. This comment gives the details.

Sonatype released Nexus 3.94.3 with container images that no longer
trust the compromised eMudhra intermediate CAs. The update stays on
the 3.94 line, so it does not need the required base telemetry of
Nexus 3.97 and later.

Bump the bundle version to 3.11.3.
@JayDoubleu
Jay W (JayDoubleu) requested a balanced review from Copilot October 28, 2026 10:14
@github-actions

Copy link
Copy Markdown

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 4c83b52.

Copilot AI 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.

🟢 Approval recommended

No active review issues are recorded for the Nexus image and bundle patch update.

No open issues 🎉

What changed in this PR

Updates the Nexus shared-service image to address compromised eMudhra certificate chains while staying on the 3.94 release line, avoiding the mandatory telemetry introduced in 3.97.

Changes:

  • Updates Nexus from 3.94.0 to 3.94.3 and the bundle from 3.11.2 to 3.11.3.
  • Adds an Unreleased bug-fix entry linked to issue #5276.

The PR reports successful local TLS and container-upgrade tests; Azure bundle deployment remains untested.

File Description
templates/​shared_services/​sonatype-nexus-vm/​porter.yaml Updates the Nexus image tag and bundle patch version.
CHANGELOG.md Records the certificate-trust fix and bundle version.

Review effort: Balanced

@JayDoubleu

Copy link
Copy Markdown
Collaborator Author

/test-shared-services accept_nexus_eula

@JayDoubleu
Jay W (JayDoubleu) marked this pull request as ready for review October 28, 2026 10:17
@JayDoubleu
Jay W (JayDoubleu) requested a review from a team as a code owner October 28, 2026 10:17
@github-actions

Copy link
Copy Markdown

🤖 pr-bot 🤖

🏃 Running shared service tests: https://github.com/microsoft/AzureTRE/actions/runs/40670903808

(in response to this comment from Jay W (@JayDoubleu))

@JayDoubleu

Copy link
Copy Markdown
Collaborator Author

/test-force-approve

The shared service tests in run 40670903808 passed for Nexus. This PR changes only the Nexus bundle.

Job Result
Run E2E Tests (Smoke) Passed
Run E2E Tests (nexus) Passed
Run E2E Tests (other) 3 passed, 1 failed

In the other job, the firewall, Gitea and admin VM tests passed. The Airlock notifier test failed during the delete of the notifier. The install and the update of the notifier completed. One poll of the delete operation got HTTP 500 from the API, with an empty body, and the E2E poll does not retry after HTTP 500. This PR does not change the Airlock notifier or the API, so the failure is not related to this PR.

The symptom is the same as in #5202, and the notifier failure is investigated separately. The API logs for this time are not available, because the API telemetry did not reach Application Insights in this environment.

@github-actions

Copy link
Copy Markdown

🤖 pr-bot 🤖

✅ Marking tests as complete (for commit 4c83b52)

(in response to this comment from Jay W (@JayDoubleu))

@JayDoubleu
Jay W (JayDoubleu) merged commit 2952b8a into microsoft:main Oct 28, 2026
11 checks passed
@JayDoubleu
Jay W (JayDoubleu) deleted the fix/nexus-3.94.3-emudhra branch October 28, 2026 14:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

The Nexus image trusts the compromised eMudhra intermediate CAs

4 participants