CVE-2013-2273 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-2273 : bitcoind and Bitcoin-Qt before 0.4.9rc1, 0.5.x before 0.5.8rc1, 0.6.0 before 0.6.0.11rc1, 0.6.1 through 0.6.5 before 0.6.5rc1, and 0.7.x before 0.7.3rc1 make it easier for remote attackers to obtain potentially sensitive information about returned change by leveraging certain predictability in the outputs of a Bitcoin transaction. CVE-2013-2292 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-2292 : bitcoind and Bitcoin-Qt 0.8.0 and earlier allow remote attackers to cause a denial of service (electricity consumption) by mining a block to create a nonstandard Bitcoin transaction containing multiple OP_CHECKSIG script opcodes. CVE-2013-2293 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-2293 : The CTransaction::FetchInputs method in bitcoind and Bitcoin-Qt before 0.8.0rc1 copies transactions from disk to memory without incrementally checking for spent prevouts, which allows remote attackers to cause a denial of service (disk I/O consumption) via a Bitcoin transaction with many inputs corresponding to many different parts of the stored block chain.
CVE-2013-2292 should get another bug, as it is still unresolved.
CVE-2013-2293 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2293): The CTransaction::FetchInputs method in bitcoind and Bitcoin-Qt before 0.8.0rc1 copies transactions from disk to memory without incrementally checking for spent prevouts, which allows remote attackers to cause a denial of service (disk I/O consumption) via a Bitcoin transaction with many inputs corresponding to many different parts of the stored block chain. CVE-2013-2292 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2292): bitcoind and Bitcoin-Qt 0.8.0 and earlier allow remote attackers to cause a denial of service (electricity consumption) by mining a block to create a nonstandard Bitcoin transaction containing multiple OP_CHECKSIG script opcodes. CVE-2013-2273 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2273): bitcoind and Bitcoin-Qt before 0.4.9rc1, 0.5.x before 0.5.8rc1, 0.6.0 before 0.6.0.11rc1, 0.6.1 through 0.6.5 before 0.6.5rc1, and 0.7.x before 0.7.3rc1 make it easier for remote attackers to obtain potentially sensitive information about returned change by leveraging certain predictability in the outputs of a Bitcoin transaction. CVE-2013-2272 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-2272): The penny-flooding protection mechanism in the CTxMemPool::accept method in bitcoind and Bitcoin-Qt before 0.4.9rc1, 0.5.x before 0.5.8rc1, 0.6.0 before 0.6.0.11rc1, 0.6.1 through 0.6.5 before 0.6.5rc1, and 0.7.x before 0.7.3rc1 allows remote attackers to determine associations between wallet addresses and IP addresses via a series of large Bitcoin transactions with insufficient fees.
Luke can you identify which ones we should keep on the tree and which ones we should drop?
net-p2p/bitcoind, net-p2p/bitcoin-qt 0.8.1 are now in the tree.
(In reply to comment #4) > net-p2p/bitcoind, net-p2p/bitcoin-qt 0.8.1 are now in the tree. Note that 0.8.1 did not fix any of the vulnerabilities in this bug...
(In reply to comment #5) > (In reply to comment #4) > > net-p2p/bitcoind, net-p2p/bitcoin-qt 0.8.1 are now in the tree. > > Note that 0.8.1 did not fix any of the vulnerabilities in this bug... Thanks wasn't certain, hence comment #3
@maintainers: ping, does 0.8.3 fix these issues?
https://en.bitcoin.it/wiki/CVEs
This should be closed.
@security team. go ahead and vote on glsa. we're done.
Vulnerable packages have been gone for over 2 years so no GLSA.
