π‘οΈ Sentinel: [HIGH] Add security headers & fix CORS #35
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.
π‘οΈ Sentinel: [HIGH] Add security headers & fix CORS
π¨ Severity: HIGH
π‘ Vulnerability:
Access-Control-Allow-Originwas not returned for allowed origins on non-preflight requests due to middleware ordering.π― Impact:
π§ Fix:
src/security-headers.tsmiddleware with strict CSP (default-src 'none'), HSTS, and other headers.src/http-transport.tsto apply security headers.src/http-transport.tsto set CORS headers before early-exit checks, ensuring valid origins work.β Verification:
npm testpasses.New tests in
src/security-headers.test.tsandsrc/testing/http-integration.test.tsverify headers are present.PR created automatically by Jules for task 12447974312424747695 started by @davidruzicka