Resonance Security reviewed Primex Finance on 14 Oct 2024: 7 findings, 1 critical; 6 marked fixed, 1 open.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 0 | 2 |
| Medium | 0 | 0 | 1 |
| Low | 1 | 0 | 2 |
The function _swapWithArbitraryDex(), although private, can be called indirectly by users with malicious inputs that are note validated properly. One of the inputs is _params.dexRouter which is used as the target address of an external function call, making it possible for a malicious user to craft arbitrary transactions with input parameters that could damage the entire protocol.There are multiple attack vectors associated with having this functionality enabled, mostly relating to the fact that it is possible for an attacker to impersonate the vulnerable smart contract. More specifically, it may be possible to drain the contract of all its funds, native or tokenized, as well as perform unauthorized actions acting as the DexAdapter. By taking into consideration the permissions and authorized actions that can be taken as DexAdapter, the impact may be more or less severe.As an example, the provided proof of concept can be used to drain the contract DexAdapter of all its NATIVE_CURRENCY. Furthermore, by using a combination of calls, delegate calls and reentrancy, a malicious smart contract may abuse the doApprove() function to gain access to tokens owned by DexAdapter.
The report names a repository or files. Open the report to see its scope.
18 projects reviewed · 25 reports · latest Aug 2025
See Resonance Security’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us