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

Adding a security vulnerability that was disclosed in the public #371

Closed
mcollina opened this issue Aug 7, 2018 · 1 comment
Closed

Adding a security vulnerability that was disclosed in the public #371

mcollina opened this issue Aug 7, 2018 · 1 comment
Assignees
@mcollina
Labels
vulnerabilities

Comments

@mcollina
Copy link
Member

mcollina commented Aug 7, 2018

In moscajs/aedes#211 a security vulnerability was posted in the public. In moscajs/aedes#212 it was fixed, and I've just released that fix.

I would like to get this added to the database, and I would definitely need a CVE. Should I pass through H1 anyway, or should I just send a PR?
@lirantal
Copy link
Member

lirantal commented Aug 7, 2018

per the policy we can just PR to the repo the vulnerability. however, if you don't have already a CVE assigned for that then we'll need to request that manually. I suggest you to PR the report and I'll request it for you through the H1 platform.

@mcollina mcollina mentioned this issue Aug 7, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcollina mcollina

Labels
vulnerabilities
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mcollina @lirantal