Repository navigation
Stop trusting the roots behind the compromised eMudhra intermediates - #179
Merged
Merged
Conversation
Debian's ca-certificates 20250419+deb13u1 drops emSign ECC Root CA - G3 and Comodo AAA Services root, which the compromised eMudhra intermediates (and their Sectigo cross-signs) chain to. Images built before that update still trust them. Rebuild both images and fail the build if either root is still in the system trust store. Bump COLLECTOR_VERSION to 1.1.51.
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.
The private keys of eight eMudhra intermediate CAs are recoverable (details). They chain to emSign ECC Root CA - G3 and, through Sectigo cross-signs, to Comodo AAA Services root.
The published
collector:latestandcollector-ebpf:latestimages shipca-certificates 20250419and accept certificates issued by the compromised intermediates. Debian's fix,20250419+deb13u1in trixie-security, removes both roots.Changes
ca-certificatesin the trust-store step. A cached install layer from before the fix can't keep the old bundle./etc/ssl/certs.COLLECTOR_VERSIONgoes to 1.1.51 so a new release is built.Verification
Run on
debian:13.5-slimwith the changed step:20250419+deb13u1, the build passes. curl rejects both test hosts (dv-g3b-emudhra,dv-g3b-aaa-emudhra) and still reaches telemetry.betterstack.com.ca-certificates=20250419pinned, the build fails.Not covered
The Vector 0.47.0 binary embeds its own Mozilla root list (rustls / webpki-roots), which still includes both roots. Vector's main HTTP sinks use OpenSSL and the system store, so this PR fixes them. Components that use the embedded list are not fixed; the likeliest is the MongoDB driver. Closing that needs a Vector upgrade or an explicit CA file on those components, tracked separately.