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 4, 2023
· 0 comments
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA valid Medium severity issueRewardA payout will be made for this issue
After extensive discussion with the sponsors, it's been realised that Hubble values stablecoins at $1 forever and assumes it (potentially they in the case where more stablecoins are integrated in the future) never depegs, Do note that having a constant value for any stablecoin easily allows malicious usage of the protocol once a particular stable depegs, leaving the protocol to hold potential worthless tokens, in the event that the stablecoin depegs and never gets back to it's peg, even if it gets back to peg, while it was not pegged 1:1 malicious actors can easily game Hubble and make ill-gotten gains
Vulnerability Detail
See summary, and then note that the stablecoin most likely relied on within Hubble is USDC, being it's it's gas token, USDC has had multiple occurences of depegs, in one instance which happened around 4 motnhs ago (as at the time of writing this report) it depegged to a whooping 87 cents for a dollar, sorce here which means that if someone provided USDC to mint VUSD, they make an outrageous profit ~15%, i.e provide $100k worth of tokens to mint a$114,943 worth of VUSD, note that this USDC depeg, caused a storm in the market and even triggered the depegging of other s notable dollar-pegged stablecoins: DAI, USDD, and USDP, though not being a common occurence one inaccurate encounter of a serious depeg could severely deter protocol
Impact
See summary + Vulnerability detail, but in short in the case where the market price of a stablecoin drops the protocol still assumes it to be pegged
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` labelMediumA valid Medium severity issueRewardA payout will be made for this issue
Bauchibred
medium
Hubble assumes stablecoins never depeg
Summary
After extensive discussion with the sponsors, it's been realised that Hubble values stablecoins at $1 forever and assumes it (potentially they in the case where more stablecoins are integrated in the future) never depegs, Do note that having a constant value for any stablecoin easily allows malicious usage of the protocol once a particular stable depegs, leaving the protocol to hold potential worthless tokens, in the event that the stablecoin depegs and never gets back to it's peg, even if it gets back to peg, while it was not pegged
1:1
malicious actors can easily game Hubble and make ill-gotten gainsVulnerability Detail
See summary, and then note that the stablecoin most likely relied on within Hubble is USDC, being it's it's gas token, USDC has had multiple occurences of depegs, in one instance which happened around 4 motnhs ago (as at the time of writing this report) it depegged to a whooping 87 cents for a dollar, sorce here which means that if someone provided USDC to mint VUSD, they make an outrageous profit ~15%, i.e provide $100k worth of tokens to mint a$114,943 worth of VUSD, note that this USDC depeg, caused a storm in the market and even triggered the depegging of other s notable dollar-pegged stablecoins: DAI, USDD, and USDP, though not being a common occurence one inaccurate encounter of a serious depeg could severely deter protocol
Impact
See summary + Vulnerability detail, but in short in the case where the market price of a stablecoin drops the protocol still assumes it to be pegged
Code Snippet
Tool used
Recommendation
Consistently fetch the real price feed of all assets, USDC/USD can be found here
Duplicate of #69
The text was updated successfully, but these errors were encountered: