The bitcoin software was written with the assumption that it is impossible to create a transaction with a hash that is identical to that of a previous transaction. One can create a coinbase transaction that is identical to a previous coinbase, implying it has the same hash. Bitcoin does not check whether that previous hash already exists but simply overwrites it in its transaction index database. When a block that contained such a duplicate is reverted (during a reorganisation), the index entry is deleted entirely. If the original transaction was not yet spent, it has now become unspendable. Solution: Upgrade to version 0.5.3_rc3 or later Upstream Commit: https://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable References: http://sourceforge.net/mailarchive/forum.php?thread_name=CAPg%2BsBhmGHnMResVxPDZdfpmWTb9uqD0RrQD7oSXBQq7oHpm8g%40mail.gmail.com&forum_name=bitcoin-development Luke, one of the maintainers for bitcoind and bitcoin-qt has added that 0.5.3-final should be out around the 12th and he would like to request stabilization for final. I will still be whiteboarding [stable] though and we can bump by Monday if that seems reasonable to all.
0.4.4 (bitcoind only), 0.5.0.4, and 0.5.3 are released and committed to the main tree. Please stabilize at least one ASAP so the affected 0.5.1 can be removed.
The vulnerable ebuilds have been removed from the tree. The newer ebuilds added incorporate the fix
@arch teams, please stabilize the following two ebuilds: net-p2p/bitcoind-0.5.3 net-p2p/bitcoin-qt-0.5.3
x86: =net-p2p/bitcoind-0.5.3: ok =net-p2p/bitcoin-qt-0.5.3: ok
amd64 stable
x86 stable. Thanks Mikle
New vuln: bug 415973
For historical reference, this is CVE-2012-1909
Thanks, everyone. GLSA vote: no.
CVE-2012-1909 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-1909): The Bitcoin protocol, as used in bitcoind before 0.4.4, wxBitcoin, Bitcoin-Qt, and other programs, does not properly handle multiple transactions with the same identifier, which allows remote attackers to cause a denial of service (unspendable transaction) by leveraging the ability to create a duplicate coinbase transaction.
Thanks, folks. GLSA Vote: no, too. Closing noglsa.