0

Scenario:

I have two proxies:

  1. Root Proxy, this is created during deployment
  2. Secondary proxies, this is created at start of each transaction, and is initialized with the context of the transaction

Both are OpenZepplin transparent proxies.

Problem

The secondary proxy initializer needs to be guarded, such that only the primary proxy can call it. I cannot figure out how the secondary proxy can be aware of the address of the primary proxy?

..And, We want to do this because :

  1. The secondary proxy is initialized with an array of contract addresses to execute
  2. delegateCalls are being made in the context of the secondary proxy
  3. so, we want to be safe against a malicious contract injected into the initializer, which calls a self-destruct, destroying the whole secondary proxy.

any help would be great! :)


Note:

https://github.com/crytic/slither/wiki/Detector-Documentation#unprotected-upgradeable-contract

We started this analysis after Slither scan gave us this vulnerability on unprotected upgradable contract

1
  • Hiya. Could you please post your code
    – immaxkent
    Commented Aug 8, 2023 at 8:43

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.