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

A Security vulnerability to report #1675

Open
Al1ex opened this issue Dec 31, 2020 · 7 comments
Open

A Security vulnerability to report #1675

Al1ex opened this issue Dec 31, 2020 · 7 comments

Comments

@Al1ex
Copy link

Al1ex commented Dec 31, 2020

Hello, I found a security vulnerabilities. I want to know how to safely submit it to the project party.Or you can contact me through TG(@RedTeamPing).

@jcvernaleo
Copy link
Member

@Al1ex Hi, thanks for the desire for safety here. If you want, you can email me and encrypt it (depending on how sensitive you feel it is).. My email address is in a lot of the btcd commits and merges. You can find my gpg key on the usual servers.

@Al1ex
Copy link
Author

Al1ex commented Jan 1, 2021

OK

@Al1ex
Copy link
Author

Al1ex commented Jan 1, 2021

@jcvernaleo hello, I have submit this vulnerability report to you email.please check it.

@xtremebeing
Copy link

Any update on this? What is the severity and impact?

@jcvernaleo
Copy link
Member

@xtremebeing Impact is minor. rpc related and crashes node at worst. Fixing it is on my list for the next release.

@JeremyRand
Copy link
Contributor

Hi, thanks for the desire for safety here. If you want, you can email me and encrypt it (depending on how sensitive you feel it is).. My email address is in a lot of the btcd commits and merges. You can find my gpg key on the usual servers.

@jcvernaleo The only OpenPGP key of yours that I see on keyservers seems to be 1024-bit DSA, which is dangerously insecure. Is there a way to report a vulnerability to you with better cryptographic security than that?

@jcvernaleo
Copy link
Member

@JeremyRand sorry for the slow reply. You are correct, that key is horribly old and more than a bit embarrassing. I'll get an updated key in the next few days and will reply to you here about it.

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

4 participants