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

Questions regarding CVE-2019-19479 #3132

Closed
utkarsh2102 opened this issue Dec 15, 2019 · 2 comments
Closed

Questions regarding CVE-2019-19479 #3132

utkarsh2102 opened this issue Dec 15, 2019 · 2 comments

Comments

@utkarsh2102
Copy link

@utkarsh2102 utkarsh2102 commented Dec 15, 2019

Hiya,
It is pretty annoying (& often irritating) that we can't access the detailed report even when the bugs have been made public (and is fixed).

That said, I would heartily request the relevant information for CVE-2019-19479 so I/we can actually reproduce the bug (accordingly) and see it's significance in the packages shipped by different distributions (I'm primarily concerned with Debian).

@oliverchang

This comment has been minimized.

Copy link
Contributor

@oliverchang oliverchang commented Dec 16, 2019

Hi, while the detailed report isn't available, you can download the reproducer after the report is public by clicking the "Reproducer testcase" link in the monorail report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18693

@utkarsh2102

This comment has been minimized.

Copy link
Author

@utkarsh2102 utkarsh2102 commented Dec 16, 2019

Hah, thanks!

while the detailed report isn't available..

That said, wouldn't it make more sense if the whole report could me made more "open" and available at least after the issue has been made public and is fixed?
What's the point of keeping it hidden anyway?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.