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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a security policy #1576

Closed
JamieSlome opened this issue Aug 2, 2022 · 3 comments
Closed

Add a security policy #1576

JamieSlome opened this issue Aug 2, 2022 · 3 comments

Comments

@JamieSlome
Copy link

Hello 馃憢

I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@lethanhtrung22) has found a potential issue, which I would be eager to share with you.

Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.

Looking forward to hearing from you 馃憤

(cc @huntr-helper)

@essen
Copy link
Member

essen commented Aug 2, 2022

You can send me an email at contact@ninenines.eu if you want.

If this is related to the distribution cookie, please see this comment: #1574 (comment)

@JamieSlome
Copy link
Author

Thanks for the follow-up @essen :)

Happy to create a SECURITY.md with this e-mail address for you 馃憤

Just for reference, the report can be found directly here:
https://huntr.dev/bounties/ffd5c11f-aec1-476c-823f-0fcca493d179/

It is private and only accessible to maintainers with repository write permissions.

@essen
Copy link
Member

essen commented Aug 2, 2022

That's exactly the same issue I linked, please read the comment. This is not a security vulnerability in Cowboy, the distribution cookie is meant to separate clusters, not to provide authentication. It is up to product developers to configure, expose or implement restrictions depending on their needs.

@essen essen closed this as completed Aug 2, 2022
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

2 participants