Skip to content

multiple evaluation of contract address in call

Moderate
charles-cooper published GHSA-4v9q-cgpw-cf38 Jun 6, 2022

Package

pip vyper (pip)

Affected versions

<0.3.4

Patched versions

0.3.4

Description

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

6b4d8ff

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

Severity

Moderate

CVE ID

CVE-2022-29255

Weaknesses

No CWEs