-
Notifications
You must be signed in to change notification settings - Fork 288
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 Vulnerabilities in Bludit - Please get in touch #1556
Comments
Do security vulnerabilities explode without a user being created, or do you always need an admin or a user to exploit them? |
Hi @dignajar, what is the current status of the fixes for the security vulnerabilities I disclosed on 2024-01-24 via email. If you need further information or if I should help you with the fixes, please get in touch with me (preferably as a reply to my initial email). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear @dignajar,
I would like to kindly ask you to get in touch with me regarding the security vulnerabilities I reported to you on 2024-01-24 via email. In addition, I suggest that a
security.md
file is created in this repository in order to simplify the process of reporting Bludit vulnerabilities.I am always happy to help if you need advice for implementing the security fixes.
Best,
Andreas
The text was updated successfully, but these errors were encountered: