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.

Sign up for GitHub

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

Jump to bottom

Please fix security issues CVE-2017-9224, CVE-2017-9225, CVE-2017-9226, CVE-2017-9227, CVE-2017-9228, CVE-2017-9229 #64

Closed
yurivict opened this issue Jul 7, 2017 · 2 comments
Closed

Please fix security issues CVE-2017-9224, CVE-2017-9225, CVE-2017-9226, CVE-2017-9227, CVE-2017-9228, CVE-2017-9229 #64

yurivict opened this issue Jul 7, 2017 · 2 comments

Comments

@yurivict
Copy link

yurivict commented Jul 7, 2017

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9224
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9225
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9226
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9227
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9228
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9229

If they are already fixed, you should add the note in the README file that they are fixed. Otherwise various systems will be flagging oniguruma as vulnerable.
@kkos
Copy link
Owner

kkos commented Jul 8, 2017

Thank you.
I wrote that these issues were fixed into README and README.md.

@yurivict
Copy link
Author

yurivict commented Jul 8, 2017

Thanks!

@yurivict yurivict closed this as completed Jul 8, 2017
@fan1x fan1x mentioned this issue May 13, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yurivict @kkos