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

Continuous fuzzing #3038

Closed
AdamKorcz opened this issue May 14, 2020 · 2 comments
Closed

Continuous fuzzing #3038

AdamKorcz opened this issue May 14, 2020 · 2 comments
Labels
area/build Build or GithubAction/CI issues type/feature Feature request type/security Security related

Comments

@AdamKorcz
Copy link
Contributor

Summary

I have been fuzzing Argo, and I would like to contribute my fuzzer to Argo. The fuzzer runs locally, and I have managed to get it running on oss-fuzz's infrastructure as well. I would suggest that continuous fuzzing is implemented into Argos via oss-fuzz. This will allow the current fuzzer as well as all future fuzzers continuously in search for bugs.
Continuous fuzzing has been proven to find bugs over time. A bug took several CPU years of fuzzing to find.

If Argo is accepted into the oss-fuzz project and a bug is found, maintainers on the email list receive a detailed bug report. The service is offered free of charge with an implied expectation that the bugs are fixed, so that the resources spent on fuzzing Argo are put to good use.

I will be glad to implement Argo into oss-fuzz. All I need are the email addresses to add to the mailing list of the bug reports. This list is public and can be changed at any time.

Motivation

Fuzzing is a technique that has proven effective in find bugs including vulnerabilities.

Proposal

We take two steps:

  1. I contribute my fuzzer here on Argos repository.
  2. An application to integrate into oss-fuzz is setup using the fuzzer on Argos own repository.

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@AdamKorcz AdamKorcz added the type/feature Feature request label May 14, 2020
@alexec alexec added epic/tech-debt and removed type/feature Feature request labels Apr 16, 2021
@stale

This comment was marked as resolved.

@stale stale bot added the wontfix label Jun 16, 2021
@stale stale bot closed this as completed Jun 23, 2021
@agilgur5 agilgur5 added type/feature Feature request type/security Security related area/build Build or GithubAction/CI issues labels Sep 24, 2024
@agilgur5
Copy link
Contributor

For posterity, some fuzzers were added to the CNCF fuzzing repo: https://github.com/cncf/cncf-fuzzing/tree/07bfece/projects/argo

See also #7823 and #12031

@argoproj argoproj locked as resolved and limited conversation to collaborators Sep 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/build Build or GithubAction/CI issues type/feature Feature request type/security Security related
Projects
None yet
Development

No branches or pull requests

4 participants
@alexec @agilgur5 @AdamKorcz and others