July 20, 2026

Capitalizations Index – B ∞/21M

CVE-2018-17144 Full Disclosure

CVE-2018-17144 Full Disclosure

Cve-2018-17144 full disclosure

CVE-2018-17144, a fix for which was released on September 18th in bitcoin Core versions 0.16.3 and 0.17.0rc4, includes both a Denial of Service component and a critical inflation vulnerability. It was originally reported to several developers working on bitcoin Core, as well as projects supporting other cryptocurrencies, including ABC and Unlimited on September 17th as a Denial of Service bug only, however we quickly determined that the issue was also an inflation vulnerability with the same root cause and fix.

In order to encourage rapid upgrades, the decision was made to immediately patch and disclose the less serious Denial of Service vulnerability, concurrently with reaching out to miners, businesses, and other affected systems while delaying publication of the full issue to give times for systems to upgrade. On September 20th a post in a public forum reported the full impact and although it was quickly retracted the claim was further circulated.

At this time we believe over half of the bitcoin hashrate has upgraded to patched nodes. We are unaware of any attempts to exploit this vulnerability.

However, it still remains critical that affected users upgrade and apply the latest patches to ensure no possibility of large reorganizations, mining of invalid blocks, or acceptance of invalid transactions occurs.

In bitcoin Core 0.14, an optimization was added (bitcoin Core PR #9049) which avoided a costly check during initial pre-relay block validation that multiple inputs within a single transaction did not spend the same input twice which was added in 2012 (PR #443). While the UTXO-updating logic has sufficient knowledge to check that such a condition is not violated in 0.14 it only did so in a sanity check assertion and not with full error handling (it did, however, fully handle this case twice in prior to 0.8).

Thus, in bitcoin Core 0.14.X, any attempts to double-spend a transaction output within a single transaction inside of a block will result in an assertion failure and a crash, as was originally reported.

In bitcoin Core 0.15, as a part of a larger redesign to simplify unspent transaction output tracking and correct a resource exhaustion attack the assertion was changed subtly. Instead of asserting that the output being marked spent was previously unspent, it only asserts that it exists.

Thus, in bitcoin Core 0.15.X, 0.16.0, 0.16.1, and 0.16.2, any attempts to double-spend a transaction output within a single transaction inside of a block where the output being spent was created in the same block, the same assertion failure will occur (as exists in the test case which was included in the 0.16.3 patch). However, if the output being double-spent was created in a previous block, an entry will still remain in the CCoin map with the DIRTY flag set and having been marked as spent, resulting in no such assertion. This could allow a miner to inflate the supply of bitcoin as they would be then able to claim the value being spent twice.

Timeline for September 17, 2018: (all times UTC)

  • 14:57 anonymous reporter reports crash bug to: Pieter Wuille, Greg Maxwell, Wladimir Van Der Laan of bitcoin Core, deadalnix of bitcoin ABC, and sickpig of bitcoin Unlimited.
  • 15:15 Greg Maxwell shares the original report with Cory Fields, Suhas Daftuar, Alex Morcos and Matt Corallo
  • 17:47 Matt Corallo identifies inflation bug
  • 19:15 Matt Corallo first tries to reach slushpool CEO to have a line of communication open to apply a patch quickly
  • 19:29 Greg Maxwell timestamps the hash of a test-case which demonstrates the inflation vulnerability (a47344b7dceddff6c6cc1c7e97f1588d99e6dba706011b6ccc2e615b88fe4350)
  • 20:15 John Newbery and James O’Beirne are informed of the vulnerability so they can assist in alerting companies to a pending patch for a DoS vulnerability
  • 20:30 Matt Corallo speaks with slushpool CTO and CEO and shares patch with disclosure of the Denial of Service
  • 20:48 slushpool confirmed upgraded
  • 21:08 Alert was sent to bitcoin ABC that a patch will be posted publicly by 22:00
  • 21:30 (approx) Responded to original reporter with an acknowledgment
  • 21:57 bitcoin Core PR 14247 published with patch and test demonstrating the Denial of Service bug
  • 21:58 bitcoin ABC publishes their patch
  • 22:07 Advisory email with link to bitcoin Core PR and patch goes out to Optech members, among others
  • 23:21 bitcoin Core version 0.17.0rc4 tagged

September 18, 2018:

  • 00:24 bitcoin Core version 0.16.3 tagged
  • 20:44 bitcoin Core release binaries and release announcements were available
  • 21:47 Bitcointalk and reddit have public banners urging people to upgrade

September 19, 2018:

  • 14:06 The mailing list distributes an additional message urging people to upgrade by Pieter Wuille

September 20, 2018:

  • 19:50 David Jaenson independently discovered the vulnerability, and it was reported to the bitcoin Core security contact email.

Published at Thu, 20 Sep 2018 04:00:00 +0000

Previous Article

Facebook’s Secret BLOCKCHAIN Project, New XRP Payment Method – Today’s Crypto News

Next Article

How To Start a Blog And Make Money Online – Webinar – Bucharest

You might be interested in …

Palestine May Launch Its Own Cryptocurrency as Sovereign Legal Tender

Palestine Plans Cryptocurrency as Sovereign Legal Tender

Palestinian officials are planning for the region of Palestine to receive its own digital currency within the next five years. The motivation for this stems from concerns about potential Israeli interference, Azzam Shawwa, Governor of the Palestinian Monetary Authority (PMA), told the news agency Reuters.

Palestinians have no sovereign currency of their own and use a combination of different currencies, including the euro, the dollar, the Jordanian dinar and the Israeli shekel, to conduct their daily financial transactions.

Due to the lack of a sovereign currency, Palestinian officials have little control over money supply and inflation. This is why the Palestinian Monetary Authority wants to introduce a bitcoin-like digital currency as the territory’s new legal tender, which will be called “the Palestinian Pound,” according to Shawwa.

It is the Palestinian Monetary Authority’s goal to become a fully-fledged and internationally recognized central bank for an independent Palestine. However, it is still unclear how a digital sovereign currency for Palestinians would sit with the 1994 Paris Protocol agreement. The protocol agreement gives the Palestinian Monetary Authority the functions of a central bank; however, it has not granted the institutions the right to issue its own currency. The Paris protocol recommends the use of the shekel in the region and, thereby, effectively provides Israel with a veto over the establishment of a Palestinian currency.

A sovereign digital currency, though, would make sense for Palestine. Not only would it allow the PMA to have more control over the country’s money supply and inflation, but it would also circumvent the practical challenges of delivering hard currency into the country as the PMA has no money-printing facilities.

“If we print currency, to get it into the country you would always need clearance from the Israelis and that could be an obstacle. So that is why we don’t want to go into it,” Shawwa explained to Reuters.  

While the digital Palestinian pound is planned to be issued within the next five years, this will be no easy task for Palestinian authorities, given that the Palestinian Monetary Authority has been trying for over a decade to become an internationally recognized central bank.

Another option for the Palestinian monetary situation would be to keep the current status quo of the four above-mentioned currencies in use or to officially recognize one of the these currencies as the territory’s legal tender. However, a digital sovereign currency would be the preferred choice for Palestine, according to Shawwa.

The post Palestine May Launch Its Own Cryptocurrency as Sovereign Legal Tender appeared first on Bitcoin Magazine.

Img_8168

IMG_8168

IMG_8168By carZ ! on 1980-01-01 00:00:11