VaultReader.sol sets the address of the GMX reader in its constructor.
According to integration notes of GMX:
If using contracts such as the ExchangeRouter, Oracle or Reader do note that their addresses will change as new logic is added
The issue is that this address cannot be updated after deployment. This introduces a risk, if the address of the GmxReader changes, the protocol will start using GMX outdated functionality. As this contract is responsible for extracting information from GMX to the protocol's critical functions, this extracted information can be wrong, rendering the protocol useless.
Inability to update the address of GmxReader.
Use outdated functionality.
Use of wrong values.
Manual review
Add a function that enables to update the address of the Reader.
Please read the CodeHawks documentation to know which submissions are valid. If you disagree, provide a coded PoC and explain the real likelihood and the detailed impact on the mainnet without any supposition (if, it could, etc) to prove your point.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.