Skip to content

Conversation

@sciencemanx
Copy link
Contributor

Adds

  • h2o cve
  • poc test case
  • improvements to github/docker CI

version: '1.4'
project: h2o-cve-2018-0608
target: h2o
baseimage: forallsecure/h2o-cve-2018-0608
Copy link
Member

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).

Copy link
Contributor Author

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.
Copy link
Member

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants