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

Add a Security Policy #119

Open
Ccamm opened this issue Jan 18, 2023 · 5 comments
Open

Add a Security Policy #119

Ccamm opened this issue Jan 18, 2023 · 5 comments

Comments

@Ccamm
Copy link

Ccamm commented Jan 18, 2023

Feature request

Summary

Add a security policy to this repository to explain how to privately disclose vulnerabilities. I have tried emailing the main contributor (@alexzaganelli) about a security vulnerability, but I haven't received a response yet. I do not know if the email address I sent my report to is used anymore, so it would be great to have clarification of what would be best method of communication for reporting vulnerabilities.

Why is it needed?

It will assist security researchers to privately report vulnerabilities. Professional security researchers want to have security vulnerabilities patched before details are published to inform users of the issue.

Suggested solution(s)

Add a security policy with a method for privately reporting vulnerabilities.

Related issue(s)/PR(s)

N/A

@github-actions
Copy link

Thank you!! This is your first issue on this repo

@Ccamm
Copy link
Author

Ccamm commented Jan 21, 2023

@alexzaganelli pinging again because you should do this ASAP and respond to my report (assuming your current email is me@alexzaganelli.com). The vulnerability I want to report is rated critical and everyone who is using this plugin is vulnerable.

@alexzaganelli
Copy link
Owner

Hi @Ccamm, thank you for your contribute. I'll try to do all my best during the next week. As you can imagine this is a plugin that I've written for the community, not for my own business so I need to find a bunch of time to fix this vulnerability.

Thank you again.
Alex

@Ccamm
Copy link
Author

Ccamm commented Jan 26, 2023

Hi @Ccamm, thank you for your contribute. I'll try to do all my best during the next week. As you can imagine this is a plugin that I've written for the community, not for my own business so I need to find a bunch of time to fix this vulnerability.

Thank you again. Alex

Thanks for the response. I assume that you have seen my report that I sent to me@alexzaganelli.com. Let's communicate via email, since it is a sensitive matter that I don't want to get out.

I will close this issue when a Security Policy is added, since it is needed for future security researchers to privately disclose vulnerabilities.

@rrubio
Copy link

rrubio commented Mar 4, 2024

@Ccamm was this issue resolved?

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

3 participants