DeFi Saver Exchange Vulnerability: Difference between revisions
(Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/defisaverexchangevulnerability.php}} thumb|DeFi SaverThere was a vulnerability in the DefiSaver smart contract. Some funds were under risk, however they were captured and returned through a whitehat hack. This is a global/international case not involving a specific country. == About DeFi Saver == "DeFi Saver is a one-stop dashboard for creating, managing and tracking your...") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/defisaverexchangevulnerability.php}} | {{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/defisaverexchangevulnerability.php}} | ||
{{Unattributed Citations}} | |||
[[File:Defisaver.jpg|thumb|DeFi Saver]]There was a vulnerability in the DefiSaver smart contract. Some funds were under risk, however they were captured and returned through a whitehat hack. | [[File:Defisaver.jpg|thumb|DeFi Saver]]There was a vulnerability in the DefiSaver smart contract. Some funds were under risk, however they were captured and returned through a whitehat hack. | ||
This is a global/international case not involving a specific country. | This is a global/international case not involving a specific country. | ||
<ref name="defisaverwebsite-1807" /><ref name="imtokenofficialtwitter-1808" /><ref name="slowmistmedium-1809" /><ref name="defisavertwitter-1810" /><ref name="defisavertwitter-1811" /><ref name="defisavermedium-1812" /><ref name="defisavertwitter-1813" /><ref name="etherscan-1814" /><ref name="etherscan-1815" /><ref name="mastermedium-3719" /><ref name="blocksecteammedium-3714" /><ref name="secos-3720" /> | |||
== About DeFi Saver == | == About DeFi Saver == | ||
| Line 31: | Line 33: | ||
Don't Include: | Don't Include: | ||
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed. | * Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed. | ||
* Anything that wasn't reasonably knowable at the time of the event. | * Anything that wasn't reasonably knowable at the time of the event. | ||
| Line 53: | Line 54: | ||
|- | |- | ||
|June 19th, 2020 12:00:00 AM | |June 19th, 2020 12:00:00 AM | ||
| | |Main Event | ||
| | |Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here. | ||
|- | |- | ||
| | | | ||
| Line 66: | Line 63: | ||
== Total Amount Lost == | == Total Amount Lost == | ||
The total amount lost | The total amount lost has been estimated at $30,000 USD. | ||
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie? | How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie? | ||
| Line 77: | Line 74: | ||
== Total Amount Recovered == | == Total Amount Recovered == | ||
There do not appear to have been any funds recovered in this case. | |||
What funds were recovered? What funds were reimbursed for those affected users? | What funds were recovered? What funds were reimbursed for those affected users? | ||
| Line 88: | Line 85: | ||
== References == | == References == | ||
[https://defisaver.com/ DeFi Saver] (Jul 24) | <references><ref name="defisaverwebsite-1807">[https://defisaver.com/ DeFi Saver] (Jul 24, 2021)</ref> | ||
[https://twitter.com/imTokenOfficial/status/1314126579971186688 @imTokenOfficial Twitter] (Jul 24) | <ref name="imtokenofficialtwitter-1808">[https://twitter.com/imTokenOfficial/status/1314126579971186688 @imTokenOfficial Twitter] (Jul 24, 2021)</ref> | ||
[https://slowmist.medium.com/slowmist-how-was-the-310-000-dai-of-defi-saver-users-stolen-91de37a4ade2 Slowmist How Was The 310 000 Dai Of Defi Saver Users Stolen] (Jul 24) | <ref name="slowmistmedium-1809">[https://slowmist.medium.com/slowmist-how-was-the-310-000-dai-of-defi-saver-users-stolen-91de37a4ade2 Slowmist How Was The 310 000 Dai Of Defi Saver Users Stolen] (Jul 24, 2021)</ref> | ||
[https://twitter.com/DeFiSaver/status/1274093629800361984 @DeFiSaver Twitter] (Jul 24) | <ref name="defisavertwitter-1810">[https://twitter.com/DeFiSaver/status/1274093629800361984 @DeFiSaver Twitter] (Jul 24, 2021)</ref> | ||
[https://twitter.com/DeFiSaver/status/1274787645093285890 @DeFiSaver Twitter] (Jul 24) | <ref name="defisavertwitter-1811">[https://twitter.com/DeFiSaver/status/1274787645093285890 @DeFiSaver Twitter] (Jul 24, 2021)</ref> | ||
[https://medium.com/defi-saver/disclosing-a-recently-discovered-exchange-vulnerability-fcd0b61edffe Disclosing A Recently Discovered Exchange Vulnerability] (Jul 24) | <ref name="defisavermedium-1812">[https://medium.com/defi-saver/disclosing-a-recently-discovered-exchange-vulnerability-fcd0b61edffe Disclosing A Recently Discovered Exchange Vulnerability] (Jul 24, 2021)</ref> | ||
[https://twitter.com/DeFiSaver/status/1277973869710594053 @DeFiSaver Twitter] (Jul 24) | <ref name="defisavertwitter-1813">[https://twitter.com/DeFiSaver/status/1277973869710594053 @DeFiSaver Twitter] (Jul 24, 2021)</ref> | ||
[https://etherscan.io/address/0x9523fe0d1d488cafddfb3dce28d7d177dddbc300 ExchangeRedeemer | 0x9523fe0d1d488cafddfb3dce28d7d177dddbc300] (Jul 24) | <ref name="etherscan-1814">[https://etherscan.io/address/0x9523fe0d1d488cafddfb3dce28d7d177dddbc300 ExchangeRedeemer | 0x9523fe0d1d488cafddfb3dce28d7d177dddbc300] (Jul 24, 2021)</ref> | ||
[https://etherscan.io/address/0xe05b162cd6571e825484ae95a93bfac02e64b05a DeFi Saver: Safeguard | 0xe05b162cd6571e825484ae95a93bfac02e64b05a] (Jul 24) | <ref name="etherscan-1815">[https://etherscan.io/address/0xe05b162cd6571e825484ae95a93bfac02e64b05a DeFi Saver: Safeguard | 0xe05b162cd6571e825484ae95a93bfac02e64b05a] (Jul 24, 2021)</ref> | ||
[https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/medium.com/defi-saver/disclosing-a-recently-discovered-vulnerability-d88e3b5cb67 https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/medium.com/defi-saver/disclosing-a-recently-discovered-vulnerability-d88e3b5cb67] (Oct 11) | <ref name="mastermedium-3719">[https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/medium.com/defi-saver/disclosing-a-recently-discovered-vulnerability-d88e3b5cb67 https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/medium.com/defi-saver/disclosing-a-recently-discovered-vulnerability-d88e3b5cb67] (Oct 11, 2021)</ref> | ||
[https://blocksecteam.medium.com/unlimited-approval-in-erc20-convenience-or-security-1c8dce421ed7 Unlimited Approval In Erc20 Convenience Or Security] (Oct 11) | <ref name="blocksecteammedium-3714">[https://blocksecteam.medium.com/unlimited-approval-in-erc20-convenience-or-security-1c8dce421ed7 Unlimited Approval In Erc20 Convenience Or Security] (Oct 11, 2021)</ref> | ||
[https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/www.chainnews.com/articles/790968196239.htm https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/www.chainnews.com/articles/790968196239.htm] (Oct 11) | <ref name="secos-3720">[https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/www.chainnews.com/articles/790968196239.htm https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/www.chainnews.com/articles/790968196239.htm] (Oct 11, 2021)</ref></references> | ||
Revision as of 11:17, 17 February 2023
Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' section to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!
There was a vulnerability in the DefiSaver smart contract. Some funds were under risk, however they were captured and returned through a whitehat hack.
This is a global/international case not involving a specific country. [1][2][3][4][5][6][7][8][9][10][11][12]
About DeFi Saver
"DeFi Saver is a one-stop dashboard for creating, managing and tracking your DeFi positions." "Automation can manage your leverage and protect your position from liquidation based on your input, non-custodially and trustlessly."
"Earlier today a vulnerability in the DeFi Saver Exchange was disclosed to our team."
"In order to protect user funds we performed a white hack attack to move affected funds (~$30k) to a smart contract from where only original owners can withdraw."
"We will share more details about the discovered vulnerability and the steps we will take to prevent any similar issues from happening again early next week. For the time being the Exchange has been removed from the DeFi Saver app." "If you ever used the Exchange at DeFi Saver you may need to remove token approvals in order to secure your account.Warning sign"
"All funds (~$30k) affected by the vulnerability are safe and will be returned to their owners. We performed a white hat attack to move affected funds to a smart contract from where the funds can only be withdrawn by their original owner addresses."
This is a global/international case not involving a specific country.
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| June 19th, 2020 12:00:00 AM | Main Event | Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here. |
Total Amount Lost
The total amount lost has been estimated at $30,000 USD.
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Immediate Reactions
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?
Ultimate Outcome
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
Total Amount Recovered
There do not appear to have been any funds recovered in this case.
What funds were recovered? What funds were reimbursed for those affected users?
Ongoing Developments
What parts of this case are still remaining to be concluded?
Prevention Policies
No user funds were lost.
References
- ↑ DeFi Saver (Jul 24, 2021)
- ↑ @imTokenOfficial Twitter (Jul 24, 2021)
- ↑ Slowmist How Was The 310 000 Dai Of Defi Saver Users Stolen (Jul 24, 2021)
- ↑ @DeFiSaver Twitter (Jul 24, 2021)
- ↑ @DeFiSaver Twitter (Jul 24, 2021)
- ↑ Disclosing A Recently Discovered Exchange Vulnerability (Jul 24, 2021)
- ↑ @DeFiSaver Twitter (Jul 24, 2021)
- ↑ ExchangeRedeemer | 0x9523fe0d1d488cafddfb3dce28d7d177dddbc300 (Jul 24, 2021)
- ↑ DeFi Saver: Safeguard | 0xe05b162cd6571e825484ae95a93bfac02e64b05a (Jul 24, 2021)
- ↑ https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/medium.com/defi-saver/disclosing-a-recently-discovered-vulnerability-d88e3b5cb67 (Oct 11, 2021)
- ↑ Unlimited Approval In Erc20 Convenience Or Security (Oct 11, 2021)
- ↑ https://git.secos.mobi:9930/all_projects/ethscope/Approval/defcon/-/blob/master/www.chainnews.com/articles/790968196239.htm (Oct 11, 2021)