STORAGE COLLISION BETWEEN PROXY AND IMPLEMENTATION (LACK EIP 1967)
Summary
STORAGE COLLISION BETWEEN PROXY AND IMPLEMENTATION (LACK EIP 1967)
Vulnerability Details
Storage collision because of lack of EIP1967 could cause conflicts and override sensible variables.
Impact
When you implement proxies, logic and implementation share the same storage layout. In order to avoid storage conflicts EIP1967 was proposed.(https://eips.ethereum.org/EIPS/eip-1967) The idea is to set proxy variables at fixed positions .
There is a table at OZ site that explains this scenario more in detail:
https://docs.openzeppelin.com/upgrades-plugins/1.x/proxies
section “Unstructured Storaged Proxies”
Tools Used
Recommendations
Consider using EIP1967
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.