New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Null pointer Deference in WasmBinaryBuilder::getFunctionIndexName(unsigned int) in wasm/wasm-binary.cpp #1879
Comments
This was referenced Jan 20, 2019
kripken
added a commit
that referenced
this issue
Jan 20, 2019
Merged
|
Can be broken again. git log |
|
I think those are fixed with #1887 |
kripken
added a commit
that referenced
this issue
Jan 24, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, there.
A Null pointer Deference problem was discovered in WasmBinaryBuilder::getFunctionIndexName(unsigned int) in wasm/wasm-binary.cpp. A crafted wasm input can cause segment faults and I have confirmed them with address sanitizer too.
Here are the POC files. Please use "wasm-opt $POC" to reproduce the problem.
POC.zip
git log
The ASAN dumps the stack trace as follows:
The text was updated successfully, but these errors were encountered: