WebAssembly / WebAssembly/binaryen
Binary encoding isn't fully validated
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
During parsing of binary-encoded files, the input isn't fully validated against the specification.
For example, the specification states that "known sections may [must?] not appear out of order", however, this isn't currently being verified. Most likely, an assertion failure will occur during parsing, but this isn't guaranteed.
Likewise, the specification states that "each section is optional and may appear at most once", but since sections are parsed in a loop, the latest section of a specific type will take precedence, plus any side effects from previous occurrences of that section type.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the binary-file parsing entry point and comparing section-order and duplicate-section handling with the WebAssembly binary format specification; done means malformed inputs are rejected consistently and regression coverage verifies both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100