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

Contact for security issue #318

Closed
chb9 opened this issue Sep 14, 2017 · 17 comments
Closed

Contact for security issue #318

chb9 opened this issue Sep 14, 2017 · 17 comments
Milestone

Comments

@chb9
Copy link

chb9 commented Sep 14, 2017

Hi,

I've found a serious security issue in BlogoText 3.7.5.

@remrem How can I contact (email) you privately?

@remrem
Copy link
Contributor

remrem commented Sep 14, 2017

Hi,
just created : contact at blogotext.org

@remrem
Copy link
Contributor

remrem commented Sep 16, 2017

Hi @chb9 ,
I did not receive your email, did you have time to send it?

@chb9
Copy link
Author

chb9 commented Sep 16, 2017

@remrem I just sent the mail again. Did you receive it?

@remrem
Copy link
Contributor

remrem commented Sep 16, 2017

Yep !, My bad, mail filtering ...

Thank for this report, I take a look on it right now !

@remrem
Copy link
Contributor

remrem commented Sep 16, 2017

Ok, security issue confirmed.
A big thank-you to you @chb9 for this issue, you rock!

I'll do my best to quickly push a fix and let the community know about the fix.

@chb9, If you plan to release this issue to the public domain, can you wait some time to let the community update theirs BlogoText ?
And I think you deserve a place in CONTRIBUTORS if you want (I let you push a commit).

@B4rb3rouss
Copy link
Contributor

I'm very curious to know more about this issue.

Thank you for reporting.

@chb9
Copy link
Author

chb9 commented Sep 17, 2017

If you plan to release this issue to the public domain, can you wait some time to let the community update theirs BlogoText ?

Of course. I will also request a CVE ID after you fix that issue.

And I think you deserve a place in CONTRIBUTORS if you want (I let you push a commit).

Thank you.

@remrem remrem added this to the 3.7.6 milestone Sep 17, 2017
@chb9
Copy link
Author

chb9 commented Sep 29, 2017

@remrem When do you plan to fix this issue and release a new version?

@remrem
Copy link
Contributor

remrem commented Sep 29, 2017

@chb9 Tomorrow. Not enough time in the last few days :/

@BoboTiG
Copy link
Collaborator

BoboTiG commented Sep 30, 2017

@remrem do you want I take a look?

@remrem
Copy link
Contributor

remrem commented Sep 30, 2017

@BoboTiG I'm working on this right now ;)

@remrem
Copy link
Contributor

remrem commented Sep 30, 2017

Fixed version
Again, thank you @chb9 ! If you need an official comment or documentation for your CVE ID request, @BoboTiG and me are here ;)

@B4rb3rouss
Copy link
Contributor

Thank you :)

@chb9
Copy link
Author

chb9 commented Oct 1, 2017

@remrem Thank you, I've requested a CVE ID and let you know as soon as I have it.

@remrem
Copy link
Contributor

remrem commented Oct 1, 2017

Ok, I close this issue.

@remrem remrem closed this as completed Oct 1, 2017
@chb9
Copy link
Author

chb9 commented Oct 1, 2017

CVE-2017-14957 has been assigned for this issue.

@remrem
Copy link
Contributor

remrem commented Oct 1, 2017

@chb9, thank you ;)
I've just update the release description

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants