Unlock Protocol Critical Vulnerability - Revision history

Azoundria at 18:04, 4 May 2023

2023-05-04T18:04:59Z

← Older revision		Revision as of 12:04, 4 May 2023
Line 4:		Line 4:
	[[File:Unlockprotocol.jpg\|thumb\|Unlock Protocol]]The Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost.		[[File:Unlockprotocol.jpg\|thumb\|Unlock Protocol]]The Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.<ref name="blockthreat-5482" /><ref name="unlockprotocol-6070" /><ref name="unlockprotocol-6071" /><ref name="youtube-6072" /><ref name="unlockprotocol-6073" /><ref name="etherscan-6074" /><ref name="youtube-6321" /><ref name="blockscout-6318" />
	<ref name="blockthreat-5482" /><ref name="unlockprotocol-6070" /><ref name="unlockprotocol-6071" /><ref name="youtube-6072" /><ref name="unlockprotocol-6073" /><ref name="etherscan-6074" /><ref name="youtube-6321" /><ref name="blockscout-6318" />

	== About Unlock Protocol ==		== About Unlock Protocol ==
Line 65:		Line 64:
	!Description		!Description
	\|-		\|-
	\|October 14th, 2021 ~~12:00:00 AM~~		\|October 14th, 2021
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 73:		Line 72:
	\|		\|
	\|}		\|}

			== Technical Details ==
			This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?

	== Total Amount Lost ==		== Total Amount Lost ==
Line 92:		Line 94:
	== Ongoing Developments ==		== Ongoing Developments ==
	What parts of this case are still remaining to be concluded?		What parts of this case are still remaining to be concluded?
			== Individual Prevention Policies ==
			{{Prevention:Individuals:Placeholder}}

			{{Prevention:Individuals:End}}

			== Platform Prevention Policies ==
			{{Prevention:Platforms:Placeholder}}

			{{Prevention:Platforms:End}}

			== Regulatory Prevention Policies ==
			{{Prevention:Regulators:Placeholder}}

	== Prevention ~~Policies ==~~		{{Prevention:Regulators:End}}
	~~Which policies could have prevented this event from happening?~~

	== References ==		== References ==

Azoundria at 23:55, 27 February 2023

2023-02-27T23:55:27Z

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/unlockprotocolcriticalvulnerability.php}} Unlock ProtocolThe Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost. This is a global/internati..."

2023-01-28T03:51:15Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/unlockprotocolcriticalvulnerability.php}} thumb|Unlock ProtocolThe Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost. This is a global/internati..."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/unlockprotocolcriticalvulnerability.php}}

[[File:Unlockprotocol.jpg|thumb|Unlock Protocol]]The Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost.

This is a global/international case not involving a specific country.

== About Unlock Protocol ==
"Create locks and place them anywhere you’d like to lock content. Users can purchase memberships as NFT keys that grant access to content, tickets and anything else you’d like to monetize."

"Unlock is an open source, Ethereum-based protocol designed to streamline membership benefits for online communities." "Unlock is meant to help creators find ways to monetize without relying on a middleman. It’s a protocol — and not a centralized platform that controls everything that happens on it."

"Unlock’s mission is about taking back subscription and access from the domain of middlemen — from a million tiny silos and a handful of gigantic ones — and transforming it into a fundamental business model for the web."

"The Unlock Protocol can be applied to publishing (paywalls), newsletters, software licenses or even the physical world, such as transportation systems. The web revolutionized all of these areas - Unlock will make them economically viable."

"[A] vulnerability was introduced in a UDT contract upgrade on August 2nd 2021 and discovered on October 14th around 1045AM ET."

"The UDT contract did not originally included a burn function. However, in order to support governance functions, we had to perform an upgrade to our contract on August 2nd 2021. Even though we only used OpenZeppelin's library for the UDT contract (and did not write any logic ourselves), the upgrade required some very specific work to support changes in the contract storage between the version we deployed in November 2020 and the ERC20 version used for governance. Specifically, we had to flatten the OpenZeppelin library in order to apply some patches to avoid storage slot conflicts."

"In a nutshell, the vulnerability allowed anyone to burn tokens from any other address. Even though this could not have resulted in funds being transferred, and we could have recovered any "burned" tokens through a contract upgrade, we believe it could have impacted the price and behavior of the protocol in ways that would have been hard to recover from."

"Fixing the vulnerability was trivial: we just rendered the burn function non operating by removing the internal call to _burn. In a subsequent deployment, we completely removed the burn function so that calling it will result in errors." "A patch was successfully deployed on the same day at about 1PM ET. The vulnerability was not exploited."

"We will add a new testing framework to test our changes as upgrades (on top of unit tests). We already leverage hardhat's amazing "local fork" feature and we will increase our use of this. We will additionally perform these tests as part of our CI cycle."

"We will perform an audit for the UDT contract. We have always considered, and this is still the case, that the funds at risk on the Unlock and PublicLock contracts (the core protocol) were in fact smaller than the cost of auditing (especially as the protocol still evolves quickly). However, this is not the case for the UDT contract. We have contacted a few firms and we will share results once we have them."

"Even though no funds were stolen, the signature issue we identified means that a lot of people who have claimed tokens for the airdrop did not actually delegate their votes. We have identified the list of all accounts that have been affected. We are pondering a way to cover the gas cost of them issuing a 2nd delegation and we'll have something to offer soon."

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.
{| class="wikitable"
|+Key Event Timeline - Unlock Protocol Critical Vulnerability
!Date
!Event
!Description
|-
|October 14th, 2021 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 ==
No funds were lost.

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 ==
Which policies could have prevented this event from happening?

== References ==
[https://www.blockthreat.io/p/blockthreat-week-42-2021 No Title] (Jan 10)

[https://unlock-protocol.com/ Unlock: The Web's new business model] (Jan 28)

[https://unlock-protocol.com/about About | Unlock: The Web's new business model] (Jan 28)

[https://www.youtube.com/watch?v=tBuMj0eRrYQ Unlock - Demo - YouTube] (Jan 28)

[https://unlock-protocol.com/blog/udt-disclosure UDT Vulnerability Disclosure | Unlock: The Web's new business model] (Jan 28)

[https://etherscan.io/tx/0x615f52d89673d41e7c5d3940beb50d586331f4664bae69556ef70b877175896c https://etherscan.io/tx/0x615f52d89673d41e7c5d3940beb50d586331f4664bae69556ef70b877175896c] (Jan 28)

[https://www.youtube.com/watch?v=6XmPcIZQV74 Unlock Protocol Hacked, What's Next and What To Expect ? - YouTube] (Feb 9)

[https://blockscout.com/xdai/mainnet/tx/0x6e9cbe9508f6d21e921aff0b6765a7bfecee5dd6eca43460a24d84a87fa13904 Transaction 0x6e9cbe9508f6d21e921aff0b6765a7bfecee5dd6eca43460a24d84a87fa13904 - Gnosis Chain Explorer] (Feb 9)

← Older revision		Revision as of 17:55, 27 February 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/unlockprotocolcriticalvulnerability.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/unlockprotocolcriticalvulnerability.php}}
			{{Unattributed Sources}}

	[[File:Unlockprotocol.jpg\|thumb\|Unlock Protocol]]The Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost.		[[File:Unlockprotocol.jpg\|thumb\|Unlock Protocol]]The Unlock Protocol is a smart contract utility which allows services to create membership systems easily. Unlock Protocol patched a critical vulnerability that could allow anyone to burn tokens from arbitrary addresses. The vulnerability was not exploited, and no funds were lost.

	This is a global/international case not involving a specific country.		This is a global/international case not involving a specific country.
			<ref name="blockthreat-5482" /><ref name="unlockprotocol-6070" /><ref name="unlockprotocol-6071" /><ref name="youtube-6072" /><ref name="unlockprotocol-6073" /><ref name="etherscan-6074" /><ref name="youtube-6321" /><ref name="blockscout-6318" />

	== About Unlock Protocol ==		== About Unlock Protocol ==
Line 95:		Line 97:

	== References ==		== References ==
	[https://www.blockthreat.io/p/blockthreat-week-42-2021 No Title] (Jan 10)		<references><ref name="blockthreat-5482">[https://www.blockthreat.io/p/blockthreat-week-42-2021 No Title] (Jan 10, 2022)</ref>

	[https://unlock-protocol.com/ Unlock: The Web's new business model] (Jan 28)		<ref name="unlockprotocol-6070">[https://unlock-protocol.com/ Unlock: The Web's new business model] (Jan 28, 2022)</ref>

	[https://unlock-protocol.com/about About \| Unlock: The Web's new business model] (Jan 28)		<ref name="unlockprotocol-6071">[https://unlock-protocol.com/about About \| Unlock: The Web's new business model] (Jan 28, 2022)</ref>

	[https://www.youtube.com/watch?v=tBuMj0eRrYQ Unlock - Demo - YouTube] (Jan 28)		<ref name="youtube-6072">[https://www.youtube.com/watch?v=tBuMj0eRrYQ Unlock - Demo - YouTube] (Jan 28, 2022)</ref>

	[https://unlock-protocol.com/blog/udt-disclosure UDT Vulnerability Disclosure \| Unlock: The Web's new business model] (Jan 28)		<ref name="unlockprotocol-6073">[https://unlock-protocol.com/blog/udt-disclosure UDT Vulnerability Disclosure \| Unlock: The Web's new business model] (Jan 28, 2022)</ref>

	[https://etherscan.io/tx/0x615f52d89673d41e7c5d3940beb50d586331f4664bae69556ef70b877175896c https://etherscan.io/tx/0x615f52d89673d41e7c5d3940beb50d586331f4664bae69556ef70b877175896c] (Jan 28)		<ref name="etherscan-6074">[https://etherscan.io/tx/0x615f52d89673d41e7c5d3940beb50d586331f4664bae69556ef70b877175896c https://etherscan.io/tx/0x615f52d89673d41e7c5d3940beb50d586331f4664bae69556ef70b877175896c] (Jan 28, 2022)</ref>

	[https://www.youtube.com/watch?v=6XmPcIZQV74 Unlock Protocol Hacked, What's Next and What To Expect ? - YouTube] (Feb 9)		<ref name="youtube-6321">[https://www.youtube.com/watch?v=6XmPcIZQV74 Unlock Protocol Hacked, What's Next and What To Expect ? - YouTube] (Feb 9, 2022)</ref>

	[https://blockscout.com/xdai/mainnet/tx/0x6e9cbe9508f6d21e921aff0b6765a7bfecee5dd6eca43460a24d84a87fa13904 Transaction 0x6e9cbe9508f6d21e921aff0b6765a7bfecee5dd6eca43460a24d84a87fa13904 - Gnosis Chain Explorer] (Feb 9)		<ref name="blockscout-6318">[https://blockscout.com/xdai/mainnet/tx/0x6e9cbe9508f6d21e921aff0b6765a7bfecee5dd6eca43460a24d84a87fa13904 Transaction 0x6e9cbe9508f6d21e921aff0b6765a7bfecee5dd6eca43460a24d84a87fa13904 - Gnosis Chain Explorer] (Feb 9, 2022)</ref></references>