-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 fixes #1216
Security fixes #1216
Conversation
These CORS headers set here are not needed and ineffective - the specific methods which are allowed are not actually used in the app, so these will have no effect. CORS headers should not be set without an explicit purpose, because it could introduce additional vulnerabilities.
…require authentication for websocket
It looks like a PR to add full CORS support was added in the meantime. I would recommend removing that PR as it significantly increases the exploitability of CSRF attacks against Flower. |
I've resolved the merge conflict relating to the CORS policy by setting the dangerous and unsafe CORS policy behind the same flag ( |
this package is not maintained by any active core developers or we don't have commit access to this. |
Ref #1209, #1217 and https://tprynn.github.io/2022/05/26/flower-vulns.html