WebAssembly / WebAssembly/wabt
The version 1.0.39 can't decomplie normaly
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 8.1k
- Forks
- 827
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 18
Description
Hello:
I'm using wabt-1.0.39 to solve the "Some Assembly Required 2" challenge in PicoCTF.
However, when I tried to decompile the wasm file using wasm-decompile.exe, I found that the encrypted string before and after compilation was the same.
This prevented me from continuing with the challenge, which is different from the process described in other tutorials.
So, I tried using version 1.0.30, and I was able to continue decompiling the encrypted string.
Is there a bug in version 1.0.39?
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
Start with the reported wasm-decompile.exe workflow and compare its output for the same wasm file under wabt 1.0.39 and 1.0.30. Establish whether the unchanged encrypted string is a reproducible regression, then use that comparison to define the expected decompilation result and verify the issue is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, wasm
- Domain
- compilers, devtools, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100