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

Validator: Combine multiple CSP warnings for the same reason #1547

Closed
erosman opened this issue Sep 17, 2017 · 3 comments
Closed

Validator: Combine multiple CSP warnings for the same reason #1547

erosman opened this issue Sep 17, 2017 · 3 comments

Comments

@erosman
Copy link
Contributor

erosman commented Sep 17, 2017

Example:

https://addons.mozilla.org/editors/review/854655/
https://addons.mozilla.org/en-US/developers/addon/threatpinch-lite/file/723979/validation

CSP:
"content_security_policy": "script-src 'self' https://www.threatminer.org https://api.passivetotal.org https://cymon.io https://www.virustotal.com https://api.xforce.ibmcloud.com https://api.shodan.io https://www.censys.io 'unsafe-eval'; object-src 'self'"

@EnTeQuAk EnTeQuAk self-assigned this Sep 19, 2017
@EnTeQuAk EnTeQuAk added this to the 2017.09.21 milestone Sep 19, 2017
@erosman
Copy link
Contributor Author

erosman commented Sep 20, 2017

Was there a change? I see an odd warning:

https://addons.mozilla.org/editors/review/855467/
https://addons.mozilla.org/en-US/developers/addon/b3-advanced-operator-search/file/725729/validation
https://addons.mozilla.org/en-US/firefox/files/browse/725729/file/manifest.json#top

"content_security_policy": "script-src 'self' 'unsafe-eval'; object-src 'self'"

Using 'eval' has strong security and performance implications.

In most cases the same result can be achieved differently, therefore it is generally prohibited
manifest.json

@EnTeQuAk
Copy link
Contributor

EnTeQuAk commented Sep 20, 2017

Yes, we are now warning for unsafe-eval too. Or rather, improved it's error message to be less confusing.

@muffinresearch muffinresearch modified the milestones: 2017.09.21, 2017.09.28 Sep 20, 2017
@erosman
Copy link
Contributor Author

erosman commented Sep 20, 2017

we are now warning for unsafe-eval too. Or rather, improved it's error message to be less confusing.

TBH, the unsafe-eval warning was more expressive than the generic eval which is used for actual eval() function.. but it is not an issue.

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

No branches or pull requests

3 participants