-
Notifications
You must be signed in to change notification settings - Fork 113
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
A security vulnerability may cause whole cluster been hijacked #700
Comments
Hi, I'm a maintainer. Which email are you using? (I mean whom are you sending it to) |
Thank you for reply! I'm using: |
@avishnu @Abhinandan-Purkait could you please forward me the email as well? Thanks |
I have forwarded it to you, please check.
…On Thu, 4 Jul 2024 at 15:06, Tiago Castro ***@***.***> wrote:
@avishnu <https://github.com/avishnu> @Abhinandan-Purkait
<https://github.com/Abhinandan-Purkait> could you please forward me the
email as well? Thanks
—
Reply to this email directly, view it on GitHub
<#700>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHUGHK3C6IFKDPCWRY35LATZKUJQ7AVCNFSM6AAAAABKK56TG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYGUZTSMBYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sorry for the rushing, may I ask is there any update on this issue? |
Issues go stale after 90d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed. |
1 similar comment
Issues go stale after 90d of inactivity. Please comment or re-open the issue if you are still interested in getting this issue fixed. |
Transferring this issue to the NDM repo, as this pertains to NDM. |
Description
Hi community! I found a vulnerability in openebs and reported it privately with respect to the security policy one week ago. But I didn't receive any response. This is not urging, I just wanted to ask if I haven't been successful in getting in touch with the maintainer (e.g. maybe the email is recognized as spam). I apologize if this issue has caused any trouble.
The text was updated successfully, but these errors were encountered: