This repository was archived by the owner on Oct 21, 2026. It is now read-only.
Repository navigation
fix(security): filter emSign trust paths from API images - #1
Closed
skyfriends wants to merge 1 commit into
Closed
skyfriends wants to merge 1 commit into
skyfriends wants to merge 1 commit into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 API image uses Node 20.7.0 with its older bundled trust store. This removes the emSign ECC G3, emSign TLS G3 when present, and AAA cross-signing anchors from the Debian CA bundle, then selects that bundle for Node through --use-openssl-ca. Both builder and runtime inherit the policy from the existing base stage. A build-time guard parses the selected bundle and rejects missing or still-affected trust.
Validation: Unchanged official Node 20.7.0 with the filtered CA bundle rejected all 12 disclosed chains through fetch and HTTPS and succeeded for six healthy controls. Positive/negative bundle guard checks, CA configuration filtering, and git diff --check passed. Docker was not run; image build and deployment remain unverified.
This is a temporary trust-root mitigation pending a compatible Node release containing the upstream intermediate-key blocklist. Certificates whose only trust path uses the removed roots are also rejected. Explicit application CA overrides and already-running processes require separate verification.
Reference: nodejs/node#66871
Desktop/manual application testing was not performed.