the hash calculated is incorrect according to EIP-712. Expression is missing a closing parenthesis ) after uint256 quantityIn
I marked this high since in all the previous audits reports whenever Type structured data hash has been used incorrectly according to EIP-712, it was marked high
Vulnerability Detail
see Summary
Impact
Type structured Hash used for orderId is calculated incorrectly and does not follow EIP-712 , but it says that protocol does.
Tri-pathi
high
ORDERREQUEST_TYPE_HASH
is calculated incorrectlySummary
since
the hash calculated is incorrect according to
EIP-712
. Expression is missing a closing parenthesis)
afteruint256 quantityIn
I marked this high since in all the previous audits reports whenever Type structured data hash has been used incorrectly according to
EIP-712
, it was marked highVulnerability Detail
see Summary
Impact
Type structured Hash used for
orderId
is calculated incorrectly and does not followEIP-712
, but it says that protocol does.Code Snippet
https://github.com/sherlock-audit/2023-06-dinari/blob/main/sbt-contracts/src/issuer/OrderProcessor.sol#L95 https://github.com/sherlock-audit/2023-06-dinari/blob/main/sbt-contracts/src/issuer/OrderProcessor.sol#L205
Tool used
Manual Review
Recommendation
Add a closing parenthesis
)
afteruint256 quantityIn