-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add h2o cve #2
base: master
Are you sure you want to change the base?
Add h2o cve #2
Conversation
version: '1.4' | ||
project: h2o-cve-2018-0608 | ||
target: h2o | ||
baseimage: forallsecure/h2o-cve-2018-0608 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please specify a duration (upper bound on what it would take to find, say on demo).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok haven't found the bug from scratch yet (ran target shortly and verified crash repro) but will update when it is found
|
||
Note: Fuzzing has some degree of non-determinism, so when you run | ||
yourself you may not get exactly this file. This is expected; your | ||
output should still trigger the memory corruption bug. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pls add how long it takes us to find. Such as:
On our test cluster, given the original seed, it takes about xxx minutes to reproduce the bug.
Adds