Repository navigation
fix(security): remediate community dependencies and request handlers - #7296
Merged
Merged
Conversation
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 ECS image and legacy dependency tree contain critical, high, and medium vulnerabilities. This moves Community App to Node 24 and patched dependencies, replaces the vulnerable build toolchain, and fixes the reported request-handling and browser injection issues.
buildvarandappvarpaths; deduplicate names withappvartaking precedence and exclude generated credential files from the image.Validation:
764d796da.Deployment configuration: register
/community-app-assets/auth0-popupon each community origin as an Auth0 callback, use RS256 for social linking, and configure Allowed Web Origins. The JWT secret must be at least 32 bytes. Confirm proxy CIDRs, additional avatar/CORS origins, and SSM/KMS access for both runtime parameter paths as documented in the README. Authenticated linking and submission checks against the configured tenant remain staging validation. No merge or deployment has been performed.