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

zip testdata: FuzzReader-raw.zip reported by clamav as Php.Exploit.CVE_2015_2331-2 #805

Closed
Shrekster opened this issue Apr 12, 2023 · 5 comments

Comments

@Shrekster
Copy link

Shrekster commented Apr 12, 2023

Not sure if this test artifact was intentionally placed as malformed data:

https://github.com/klauspost/compress/blob/master/zip/testdata/FuzzReader-raw.zip

More scans:

https://www.virustotal.com/gui/file/8b2655dc4480530e1a1d682ee27a823bcebddd1c4afb606e202e057419501e14/detection

@julio-lopez
Copy link

#763 #790 #791

@Shrekster
Copy link
Author

Appreciate all the work on this project!

@klauspost could you please clarify whether the stated test data contains intentionally malformed data / document it ? It shows up in our scans and prevents us from using the library. Thank you!

@klauspost
Copy link
Owner

klauspost commented Apr 13, 2023

@Shrekster Yes. It is fuzz test data. Seems like they like to detect zip files that expand a lot. This is a natural part of regression testing.

Not sure what you want to document. Use a better AV scanner.

@julio-lopez
Copy link

@klauspost Have you considered segregating the fuzz tests into a separate repo, so the test data is not included in dependent (downstream) projects?

Thanks again for the work on this project. It is a quality library and we appreciate that fuzz testing makes it more robust and thus secure.

@klauspost
Copy link
Owner

Yes, I've considered it. Making tests depend on external data has its own downsides and the framework for it would have to be made.

The fact that the continuous fuzzing uses it with some custom scripts, which is outside my control (and with little feedback).

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

3 participants