The Latest Bitcoin Bug Was So Bad, Developers Kept Its Full Details a Secret

 

This week’s major bitcoin bug was even worse than developers initially let on.

The bug originally rocked the bitcoin world when it was reported the vulnerability could be used to shut down a chunk of the network.

While this sounded bad enough for many, it turns out developers for Bitcoin Core kept a second, bigger part of the bug a secret. As disclosed through an official Common Vulnerabilities and Exposures (CVE) report, an attacker could have actually used it to create new bitcoin – above the 21 million hard-cap of coin creation – thereby inflating the supply and devaluing current bitcoins.

Such a perversion of the rules would, at worst, according to many, make users not trust the cryptocurrency anymore.

Because of the disastrous implications of the bug, developers decided to keep it a secret, buying themselves time to fix the exploit and urge miners and users to upgrade their software.

The CVE report written by Bitcoin Core developers explains:

And for now, the plan seems to have worked.

Over half of bitcoin’s mining hash rate has upgraded to the patched software version, meaning the attack can no longer be used, and developers are “unaware of any attempts to exploit this vulnerability,” the report states.

Who found it?

Finding such a serious bug was a stressful position for developers to be in.

According to the report, an anonymous user originally filed a report about the denial-of-service bug to top developers of Bitcoin Core and Bitcoin ABC, the main software implementation of bitcoin cash. About two hours later, Chaincode engineer and Bitcoin Core developer Matt Corallo realized the bug could have been exploited to print unlimited bitcoin.

Based on the seriousness of the vulnerability, the developers decided to keep those details secret at first.

Instead, beginning with Slush Pool, they started pushing miners to upgrade. And for bitcoin users running a full node, the call to action is the same.

“You should not run any version of Bitcoin Core other than 0.16.3. Older versions should not exist on the network. If you know anyone who is running an older version, tell them to upgrade it ASAP,” bitcoin subreddit moderator Theymos remarked in a post currently pinned to the top of the forum.

Yet, another problem exists now – the possibility of a bitcoin chain split

Since users are now running different versions of the bitcoin software, there’s a risk the network will temporarily split into two, then come back together again. Transactions on the chain running old software, then, might ultimately be lost.

While the situation is being monitored closely, Theymos thinks the risk of this happening is small. But, he argued that people should still take precautions, such as waiting longer to make sure a bitcoin transaction actually gets verified.

Theymos added:

Fake bitcoin?

What’s on some users’ minds, still though, is whether it’s possible the bug has already been exploited.

“How do we know if that vulnerability wasn’t exploited already and there is someone out there with a bunch of fake bitcoin?” asked one bitcoin user.

Luckily, Bitcoin Core contributor Pieter Wuille explained, due to the power of code, bitcoin users would have been able to detect suspicious activity by now.

When downloaded for the first time, full nodes double check every transaction made in bitcoin’s history. A node running the new software, 0.16.3, would detect the problem immediately.

Even so, questions remain regarding what would have happened if the bug wasn’t caught in time.

According to Theymos: “Even if the bug had been exploited to its full extent, the theoretical damage to stored funds would have been rolled back.”

Theymos continued, saying that rollback would be much like what happened during the so-called “value overflow incident” in 2010 when 187 billion bitcoins were created out of thin air but, ultimately, were destroyed.

Still, while Bitcoin Core, litecoin and several other coins that were based Bitcoin Core’s code have released a patch for the exploit, others have not – and might still be vulnerable to the inflation bug.

Code image via Shutterstock

Leave a Reply

Your email address will not be published. Required fields are marked *