Cube3

Resonance SecurityRepository, no commit named

Resonance Security reviewed Cube3 on 20 Oct 2023: 8 findings, 0 critical; 7 marked fixed, 1 open.

No open critical findings
Open the reportOpen Cube3’s security record
Report stored on IPFS. Content hash QmbyBNEKndswLU5HWUMosJWQRwF2nHXyo1Qh5Zj2T4K3JH

Trustblock does not review code.

Findings8

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium002
Low104
LowSignature Replay Attacks Possible When shouldTrackNonce Is FalseOpen

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.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Cube3’s security record

Cube3
Audits2 audits by 1 firmLast audit Aug 2024, by Resonance Security.
Critical findingsNo open critical findingsAcross 2 reports.
Open Cube3’s security record

Security firm

Resonance Security

18 projects reviewed · 25 reports · latest Aug 2025

See Resonance Security’s audits

Something 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