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

Mention cross-protocol attacks #43

Open
letitz opened this issue Apr 13, 2021 · 0 comments
Open

Mention cross-protocol attacks #43

letitz opened this issue Apr 13, 2021 · 0 comments

Comments

@letitz
Copy link
Collaborator

letitz commented Apr 13, 2021

@martinthomson has a point in w3ctag/design-reviews#572 (comment):

This proposal is no substitute for services providing encryption and proper access controls. This proposal does not protect adequately against true cross-protocol attacks that use either unencrypted HTTP or attacker-controlled components of TLS handshakes to attack poorly-protected servers from the vantage point of a client (we have a port number blocklist that is designed to help, but we know that too is not perfect).

This is largely true. Cross-protocol attacks would get harder because the request initiator would be constrained by the format of CORS preflight requests, but this is not intended to provide a robust protection in this case, nor would it. TLS handshakes are entirely unaffected.

We should call this out more clearly in the spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant