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

462 a duplicate of 442? #387

Closed
evilpacket opened this issue Aug 19, 2018 · 3 comments
Closed

462 a duplicate of 442? #387

evilpacket opened this issue Aug 19, 2018 · 3 comments
Assignees

Comments

@evilpacket
Copy link
Contributor

At first glance it appears that 462 is a duplicate of 442 but with information missing? cc @lirantal

@lirantal
Copy link
Member

oh that's true!
I'll go ahead and update it.

@pxlpnk maybe we can add another linter check that makes sure there aren't any duplicates? I think we can compare based on the hackerone report number

@pxlpnk
Copy link
Member

pxlpnk commented Aug 20, 2018

@lirantal do we always have a h1 report number?

@lirantal
Copy link
Member

In most of the cases yes.
The only times we don't have any H1 reference is when the vulnerability has been disclosed or fixed outside of the program and then we just PR it directly to the database.

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

No branches or pull requests

3 participants