envoyproxy/envoy

wasm: fuzz loading of Wasm modules

Open

#9,731 opened on Jan 18, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/wasmhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (PR metrics pending)

Description

While the loading of Wasm bytecode is covered by fuzzing in V8, there are a few cases (loading precompiled modules and parsing of Custom Sections) that are unique to Envoy and should be fuzzed.

Contributor guide

Research direction
Set up a fuzzer targeting the Wasm module loading functions, specifically focusing on precompiled module parsing and custom section parsing. Review existing fuzzing infrastructure in Envoy (e.g., libfuzzer integration) and add a new fuzz target for Wasm loading.
Tech stack
cpp
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30