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
heap buffer overflow in decompileCALLFUNCTION #83
Comments
|
Fix: Replace
by
I'll submit a PR after merge of #89. For the record, this issue has been assigned ID CVE-2017-11734. |
Make sure that n > 1 before checking for the previous action in the actions array, otherwise an overflow may occur. This commit fixes CVE-2017-11734 (fixes libming#83).
Make sure that n > 0 before checking for the previous action in the actions array, otherwise an overflow may occur. This commit fixes CVE-2017-11734 (fixes libming#83).
Instead of directly accessing the actions array without checks for the value of n (which may lead to heap buffer overflow etc, see libming#83 or libming#105), use the dedicated OpCode function.
Instead of directly accessing the actions array without checks for the value of n (which may lead to heap buffer overflow etc, see libming#83 or libming#105), use the dedicated OpCode function.
On libming latest version, a heap buffer overflow was found in function decompileCALLFUNCTION .
testcase : https://github.com/bestshow/p0cs/blob/master/heap-buffer-overflow-in_decompileCALLFUNCTION
Credit : ADLab of Venustech
The text was updated successfully, but these errors were encountered: