-
-
Notifications
You must be signed in to change notification settings - Fork 594
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] Reporting of a vulnerability #3509
Comments
Hello! I got your initial email, but my email forwarder mangled the message and I don't see any contact details to respond. Could you please try sending another email to that address and include your contacts so I can reach back out? Thanks! |
Hi, |
Following up on this again. I reached out to for more specifics about the issue you're seeing and haven't heard anything back. |
Sorry, we had to do create a clean writedown for you and all of us had some ...life... in between (as we told you, we are a group of students and also had an exam today). We will send you the writedown tomorrow! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Just leaving a comment to avoid that this ticket is automatically closed. I hope this is ok for you. |
That's appreciated @b4tb34r! |
Hello,
together with 1Atlas1, Garfunkl and chiefmastermind I found some vulnerabilities in Mealie. (I had to link their profiles because unfortunately the tag doesn't work)
According to your Security Policy we will send an email to ob92oy0sl@mozmail.com within the next few minutes.
We are looking forward to hearing from you,
b4tb34r, 1Atlas1, Garfunkl, chiefmastermind
The text was updated successfully, but these errors were encountered: