Skip to content
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

security: fix for major vulnerabilities #45

Merged
merged 6 commits into from
Mar 27, 2024
Merged

Conversation

castarco
Copy link
Contributor

@castarco castarco commented Mar 27, 2024

  • soft-deprecate how SRI options were defined, introduce new SRI options object
  • Introduce options to disallow SRI hashes generation for inline scripts and styles
  • Introduce allow-lists for cross-origin resources that might need SRI hash generation at runtime (SSR)

Signed-off-by: Andres Correa Casablanca <[email protected]>
Signed-off-by: Andres Correa Casablanca <[email protected]>
Signed-off-by: Andres Correa Casablanca <[email protected]>
Signed-off-by: Andres Correa Casablanca <[email protected]>
Signed-off-by: Andres Correa Casablanca <[email protected]>
Copy link

socket-security bot commented Mar 27, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@biomejs/[email protected] shell 0 130 kB dominionl
npm/@types/[email protected] None +1 2.09 MB types
npm/@vitest/[email protected] Transitive: environment, filesystem, unsafe +25 1.66 MB vitestbot
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +365 58 MB fredkschott
npm/[email protected] Transitive: environment, filesystem +12 302 kB bluwy
npm/[email protected] None 0 32.4 MB typescript-bot

🚮 Removed packages: npm/[email protected]

View full report↗︎

Copy link

socket-security bot commented Mar 27, 2024

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@biomejs/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

Signed-off-by: Andres Correa Casablanca <[email protected]>
@castarco
Copy link
Contributor Author

@SocketSecurity ignore npm/@biomejs/[email protected]

@castarco castarco merged commit 504c88b into main Mar 27, 2024
6 checks passed
@castarco castarco deleted the security-fix-csp-bypass branch March 27, 2024 16:55
@castarco castarco added bug Something isn't working csp Content-Security-Policy sri SubResource Integrity ssr Related to Server-Side-Rendered Content labels Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working csp Content-Security-Policy sri SubResource Integrity ssr Related to Server-Side-Rendered Content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant