8000 Empty (0B) Testcases for Envoy Gateway Crashes on OSS-Fuzz · Issue #13211 · google/oss-fuzz · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Empty (0B) Testcases for Envoy Gateway Crashes on OSS-Fuzz #13211

New issue

Have a question about this project? Sign up for a free GitHub account to o 8000 pen an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Open
Tracked by #5425
sudiptob2 opened this issue Apr 10, 2025 · 4 comments
Open
Tracked by #5425

Empty (0B) Testcases for Envoy Gateway Crashes on OSS-Fuzz #13211

sudiptob2 opened this issue Apr 10, 2025 · 4 comments

Comments

@sudiptob2
Copy link
Contributor

We are currently working on integrating fuzzing for Envoy Gateway and have encountered an issue. After integrating with OSS-Fuzz, three crashes were detected. However, the unminimized testcases for all three crashes are empty (0B).

Could anyone provide some guidance on how to reproduce these crashes?

Reference:
Crashes: https://oss-fuzz.com/testcases?fuzzer=libFuzzer_gateway_FuzzGatewayAPIToXDS
Fuzzer Source: https://github.com/envoyproxy/gateway/blob/main/test/fuzz/xds_fuzz_test.go

Acknowledgement:
This work is sponsored by the Linux Foundation Mentorship program.

Image
@nareddyt
Copy link
Contributor

Hi @jonathanmetzman @AdamKorcz can you take a look? We think this is an OSS fuzz issue. Every single reproducer test case has 0 bytes, but the OSS fuzz logs indicate the corpus seeding and mutations are working as expected.

Initial integration PR was merged last week - #13135

@DavidKorczynski
Copy link
Collaborator

I think in this instance it's because the bug does not reliably reproduce (see the "Reliably Reproduces" field). Can you confirm if there are issues that reliably reproduces but have no reproducer data?

@nareddyt
Copy link
Contributor

Hi @DavidKorczynski, you are correct, NONE of our crashes reliably reproduce.

We believe our fuzzers are completely deterministic, so that is surprising. But we can double check.

@jonathanmetzman
Copy link
Contributor

Yeah, I'm guessing this is an issue of the fuzzers randomly crashing. I'd try running them on your desktop for a few hours and see if they crash. My guess is they will.

@sudiptob2 sudiptob2 mentioned this issue May 29, 2025
Open
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development
3244

No branches or pull requests
4 participants
@DavidKorczynski @nareddyt @jonathanmetzman @sudiptob2
0