envoyproxy/envoy

ASSERT in the file_system_buffer fuzz test

Open

#40,530 opened on Aug 1, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/filesystemarea/fuzzingbughelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Test case: clusterfuzz-testcase-filter_fuzz_test-5460931974660096.txt

Steps to reproduce:

Copy downloaded test case file into the test/extensions/filters/http/common/fuzz/filter_corpus/ directory and run:

bazel build --config=asan -c dbg test/extensions/filters/http/common/fuzz/filter_fuzz_test
bazel-bin/test/extensions/filters/http/common/fuzz/filter_fuzz_test test/extensions/filters/http/common/fuzz/filter_corpus/clusterfuzz-testcase-filter_fuzz_test-5460931974660096.txt

Contributor guide

Research direction
Reproduce the fuzz test failure locally using the provided test case. Trace the ASSERT in the file system buffer code path. Identify the root cause by examining the handler and buffer logic.
Tech stack
ccpp
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitBazelC++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65