forked from milady-ai/milady
-
Notifications
You must be signed in to change notification settings - Fork 1
🛡️ Sentinel: [HIGH] Add Content-Security-Policy and Permissions-Policy headers #148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
Dexploarer
wants to merge
1
commit into
develop
Choose a base branch
from
sentinel-security-headers-5928814524265511167
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| ## 2025-02-18 - [API Security Headers] | ||
| **Vulnerability:** Missing Content-Security-Policy (CSP) and Permissions-Policy headers in API responses. | ||
| **Learning:** The API server also serves the static UI in production, making CSP crucial for mitigating XSS risks. Also, `bun test` requires explicit mocks for dependencies when `node_modules` are incomplete or path mappings are broken. | ||
| **Prevention:** Enforce security headers in the central CORS/headers middleware (`applyCors`) to ensure they apply to all responses. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
script-srcdirective includes'unsafe-inline'and'unsafe-eval', which significantly weakens the security posture against Cross-Site Scripting (XSS) attacks. These keywords allow the execution of inline scripts and dynamic code from strings, which are common XSS vectors. A strong Content Security Policy should avoid these to be effective.To improve this:
'unsafe-inline'and'unsafe-eval'fromscript-src. This is the most critical change.<script>...</script>oronclick="...") into separate.jsfiles served from your origin ('self').Additionally, for even stronger security:
style-srcalso contains'unsafe-inline', which should ideally be removed.img-srcandconnect-srcallow loading resources from anyhttps:source, which is very broad. Consider restricting this to specific, trusted domains.