You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Here we have full control of the |length| parameter, in 32-bits process, length * (uint32_t)sizeof(T) could overflow 32-bits integer range and results in a very small value, which then bypasses the boundary check in get_validated_pointer and returns an over-sized array_ptr.
Then we can read/write out of the bounds of the wasm memory buffer with this over-sized array_ptr.
This is a submission to EOS bug bounty program.
This bug credits to:
Yuki Chen of Qihoo 360 Vulcan Team.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
In function array_ptr_impl in Binaryen.hpp:
template
inline array_ptr array_ptr_impl (interpreter_interface* interface, uint32_t ptr, uint32_t length)
{
return array_ptr((T*)(interface->get_validated_pointer(ptr, length * (uint32_t)sizeof(T))));
}
Here we have full control of the |length| parameter, in 32-bits process, length * (uint32_t)sizeof(T) could overflow 32-bits integer range and results in a very small value, which then bypasses the boundary check in get_validated_pointer and returns an over-sized array_ptr.
Then we can read/write out of the bounds of the wasm memory buffer with this over-sized array_ptr.
This is a submission to EOS bug bounty program.
This bug credits to:
Yuki Chen of Qihoo 360 Vulcan Team.
Thank you!
The text was updated successfully, but these errors were encountered: