CVE-2021-48019

Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...

CVE-2021-48019

Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...

CVE-2021-48019

Vyper versions before 0.2.9 are vulnerable to an issue where the built-in create_forwarder_to function deploys forwarder proxies that report a fixed 4096-byte RETURNDATASIZE instead of the actual return data size. This discrepancy can lead to corrupted data if a function returns more than 4096 by...

EUVD-2021-34889

Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...

CVE-2021-48019 Vyper before 0.2.9 Incorrect RETURNDATASIZE in create_forwarder_to Proxies

Vyper before 0.2.9 deploys forwarder proxies through the built-in createforwarderto function that report a fixed 4096-byte RETURNDATASIZE rather than the actual return data size. Calls through these proxies can yield corrupted data when a function returns more than 4096 bytes without return data...

WS-2021-0077

If you are an end user of a forwarder-style proxy deployed using Vyper's built-in "createforwarderto" function AND you have a function that returns 4096 bytes AND you do no return data sanitation on the value returned, you could potentially see a data corruption issue. Otherwise, if you are...