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 with OSS-Fuzz #341

Open
firewave opened this issue Feb 22, 2024 · 2 comments
Open

integrate with OSS-Fuzz #341

firewave opened this issue Feb 22, 2024 · 2 comments
Assignees
Labels

Comments

@firewave
Copy link
Collaborator

The main downstream user Cppcheck is already integrated with OSS-Fuzz. As that is supposed to be used as a CLI application in the first place (although it also could be used as a library) and it also offers to perform the analysis in separate threads (albeit not on Windows - yet) fixing the fuzzing findings are not that crucial as they will mostly just be invalid code.

This is much different for this project though as it is supposed to be used as a library or inside another application by design. That makes stability and security a high priority. We have not encountered much in this regard in the past but that doesn't mean there are no actual things to find.

@firewave
Copy link
Collaborator Author

I already have a fuzzing client locally which I will publish in a PR soon. I have no permissions into the OSS-Fuzz integration (or this project) so somebody else needs to prepare the upstream integration.

The preliminary results also show that there are several issues in the code which can manifest in any possible way (crashes, leaks, hangs, out-of-memory).

@firewave
Copy link
Collaborator Author

firewave commented May 6, 2024

Preliminary client published as #351.

Before integrating it with OSS-Fuzz we should fix all known issues which were encountered during local fuzzing. Maybe even fix some of the known hot spots to improve the performance.

@firewave firewave self-assigned this Oct 5, 2024
@firewave firewave added the ci label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant