fix(header): Restrict csp headers#1577
Open
rudra-superrr wants to merge 3 commits intoeclipse-sw360:mainfrom
Open
fix(header): Restrict csp headers#1577rudra-superrr wants to merge 3 commits intoeclipse-sw360:mainfrom
rudra-superrr wants to merge 3 commits intoeclipse-sw360:mainfrom
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
3 participants
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.
Summary
Harden the Content-Security-Policy header in next.config.ts as recommended by CRA security assessment.
Problem
The CSP header was using insecure keywords unsafe-eval in the script-src directive unconditionally, and was missing restrictive directives like object-src.
Note: 'unsafe-inline' is retained in script-src as inline scripts are currently used in the codebase. The proper fix is to implement a nonce-based CSP- generating a per-request nonce in the middleware, propagating it via the root layout, and refactoring the inline script usages to use safe rendering patterns.
Testing
Start the server
Check headers via curl
curl -sI http://localhost:3000/ | grep -i "content-security-policy"