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.

Sign up for GitHub

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

Jump to bottom

Security concern #1170

Open
JamieSlome opened this issue Jan 28, 2022 · 2 comments
Open

Security concern #1170

JamieSlome opened this issue Jan 28, 2022 · 2 comments

Comments

@JamieSlome
Copy link

Hey there!

I belong to an open source security research community, and a member (@michaellrowley) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)
@probonopd
Copy link
Member

Thanks @JamieSlome. Will think about adding a SECURITY.md file. In the meantime, please use the mail address mentioned in README.md. Thanks!

@JamieSlome
Copy link
Author

@probonopd - thank you for your response! ⚡

I will get the two reports sent over to your e-mail address 👍

Just for reference, the two reports can be found here:

https://huntr.dev/bounties/617a70d5-e501-41dc-81a9-f65344b1183a/
https://huntr.dev/bounties/62f6a8f7-1c12-45a5-a5c8-615965475a38/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@probonopd @JamieSlome