-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
poco: Net library fuzzing #12506
poco: Net library fuzzing #12506
Conversation
tyler92 has previously contributed to projects/poco. The previous PR was #12432 |
@DavidKorczynski WDYT of this? |
If it helps: two issues were found by these fuzzers: |
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.
Ditto: #12526 (comment)
@tyler92 please coordinate with maintainers of poco
.
@obiltschnig @aleks-f Hi. Could you please help with review here? I believe these fuzzers and fuzzers that I added previously are useful. They found several issues that potentially can be considered as vulnerabilities. If you want we can consider moving them to the upstream later. |
Looks good to me and these tests are certainly very helpful. Looking forward to get more of these in the future. |
As far as I understand, the main advantage is gaining ownership of the fuzz targets (and seed corpus). This means that changes to existing fuzz targets, or even the addition of new ones, can be made directly in the upstream repository without involving the maintainers of Perhaps @DavidKorczynski can add more insights |
yes, it would be great if we could get them upstream from our perspective |
Two new fuzzing targets: