You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 7, 2024. It is now read-only.
sherlock-admin opened this issue
Jul 3, 2023
· 0 comments
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelHighA valid High severity issueRewardA payout will be made for this issue
Absence of Signature Expiry Check in LibMuon.verifyPrices()
Summary
The absence of a signature expiry check in the LibMuon.verifyPrices(). This vulnerability allows malicious parties to manipulate liquidation prices by using expired signatures, potentially leading to significant financial losses.
Vulnerability Detail
The vulnerability arises from the missing verification of signature expiry in the LibMuon.verifyPrices() function. The setSymbolsPrice function plays a crucial role in determining the valuation of assets before liquidation. However, without checking the expiry of the provided signature in the verifyPrices() function, malicious actors can manipulate liquidation prices using past signatures.
By leveraging expired signatures, an adversary can modify liquidation prices for their advantage as a partyA, partyB, or the liquidator. This malicious activity can result in severe financial losses and compromise the integrity of the liquidation process.
Impact
Exploiting the vulnerability, malicious actors can manipulate liquidation prices, potentially causing significant financial losses for parties involved in the liquidation process.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelHighA valid High severity issueRewardA payout will be made for this issue
pengun
high
Absence of Signature Expiry Check in LibMuon.verifyPrices()
Summary
The absence of a signature expiry check in the
LibMuon.verifyPrices()
. This vulnerability allows malicious parties to manipulate liquidation prices by using expired signatures, potentially leading to significant financial losses.Vulnerability Detail
The vulnerability arises from the missing verification of signature expiry in the
LibMuon.verifyPrices()
function. ThesetSymbolsPrice
function plays a crucial role in determining the valuation of assets before liquidation. However, without checking the expiry of the provided signature in theverifyPrices()
function, malicious actors can manipulate liquidation prices using past signatures.By leveraging expired signatures, an adversary can modify liquidation prices for their advantage as a partyA, partyB, or the liquidator. This malicious activity can result in severe financial losses and compromise the integrity of the liquidation process.
Impact
Exploiting the vulnerability, malicious actors can manipulate liquidation prices, potentially causing significant financial losses for parties involved in the liquidation process.
Code Snippet
https://github.com/sherlock-audit/2023-06-symmetrical/blob/main/symmio-core/contracts/libraries/LibMuon.sol#L50-L68C6
https://github.com/sherlock-audit/2023-06-symmetrical/blob/main/symmio-core/contracts/libraries/LibMuon.sol#L70-L85
https://github.com/sherlock-audit/2023-06-symmetrical/blob/main/symmio-core/contracts/facets/liquidation/LiquidationFacetImpl.sol#L38
Tool used
Manual Review
Recommendation
Duplicate of #113
The text was updated successfully, but these errors were encountered: