همهٔ گزارش‌ها
زیاد

Multiple evaluation of contract address in call in vyper

متن اصلی

نسخه‌های متأثر

بازه‌ها نیاز به بررسی دارند.

PyPIvyper
نسخه‌های متأثر
< 0.3.4
نسخهٔ اصلاح‌شده
0.3.4
PyPIvyper
نسخه‌های متأثر
<0.3.4
نسخهٔ اصلاح‌شده
0.3.4

بهره‌برداری

CVE-2022-29255

احتمال بهره‌برداری در ۳۰ روز آینده: 1.35%

FIRST EPSS · ۱۴۰۵/۰۸/۲۸

شرح آسیب‌پذیری

Impact

when a calling an external contract with no return value, the contract address could be evaluated twice. this is usually only an efficiency problem, but if evaluation of the contract address has side effects, it could result in double evaluation of the side effects.

in the following example, Foo(msg.sender).bar() is the contract address for the following call (to .foo()), and could get evaluated twice

interface Foo:
    def foo(): nonpayable
    def bar() -> address: nonpayable

@external
def do_stuff():
    Foo(Foo(msg.sender).bar()).foo()
Patches

6b4d8ff185de071252feaa1c319712b2d6577f8d

Workarounds

assign contract addresses to variables. the above example would change to

@external
def do_stuff():
    t: Foo = Foo(msg.sender).bar()
    t.foo()
References
For more information

پیوندها