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

Integrate Fuzzers into OSS-Fuzz and Expand Fuzzing Coverage #514

Open
gnbon opened this issue Jun 11, 2024 · 2 comments
Open

Integrate Fuzzers into OSS-Fuzz and Expand Fuzzing Coverage #514

gnbon opened this issue Jun 11, 2024 · 2 comments

Comments

@gnbon
Copy link

gnbon commented Jun 11, 2024

I noticed that the fuzzers added to the develop branch of libiec61850 about 2 years ago are not currently integrated into OSS-Fuzz. This means they are not being continuously run to help uncover potential vulnerabilities.

I have experience with integrating fuzzers into OSS-Fuzz and would be happy to assist in setting up the necessary configuration. By integrating the existing fuzzers and adding more fuzzers to cover additional components of the library, we can significantly improve the robustness and security of libiec61850.

I would be glad to work on a pull request that accomplishes these goals. By expanding the fuzzing coverage and leveraging the power of OSS-Fuzz, we can proactively identify and fix vulnerabilities, ensuring the long-term reliability and security of libiec61850.

Please let me know if you have any feedback or concerns regarding this. I'm excited about the opportunity to contribute to the robustness of the library through enhanced fuzzing techniques.

@mzillgith
Copy link
Contributor

Thank you for offering your help.

Yes, I would be glad when you could help on the OSS-Fuzz configuration part and help adding more fuzzers.

@gnbon
Copy link
Author

gnbon commented Jun 11, 2024

good. I'll work on it 😊

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

No branches or pull requests

2 participants