Resonance Security reviewed Cube3 on 20 Oct 2023: 8 findings, 0 critical; 7 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 | 0 |
| High | 0 | 0 | 1 |
| Medium | 0 | 0 | 2 |
| Low | 1 | 0 | 4 |
The function validateSignature() in the signature module is used for validating the signature present in the cube3SecurePayload. This signature is generated with multiple input parameters, while bearing in mind two important variables. One of them is a boolean value identifying whether nonce tracking is enabled or not, and another is the respective nonce if the tracking is indeed enabled.The fact that it is possible for a customer to choose whether they enable nonce tracking or not, a possibility to be vulnerable to signature replay attacks is presented. When nonce tracking is disabled, signatures can be replayed.For example, if a customer protected function implements logic for a user to receive 10 tokens, but nonce tracking was forgetfully left disabled, the same user can use the same signature and retrieve 10 more tokens an infinite number of times.
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