Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Parsing of table may take too long

Open
#92 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, wasm

Research direction

Start by locating the eos-vm parser code that fully instantiates a table while reading a wasm module, then inspect how nodeos validation currently bounds table sizes. Reproduce the issue with a small wasm declaring a table of 2^32-1 elements; done means parsing no longer permits an unbounded allocation and the behavior is covered by a regression check.

Written by the indexing model from the issue text.

Description

The table is fully instantiated by the parser, which may cause it to create a vector of 2^32-1 elements when parsing a small wasm, leading to potential DOS attacks. This is safe in nodeos for now, because the size of the table is bounded by validation, before eos-vm sees it.

Dominant language
C++
Stars
198
Forks
62
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EOSIO/eos-vm

All issues in EOSIO/eos-vm

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.