{"type":"rich","version":"1.0","author_name":"npub1a3zpmn53lhv8jv7vjg3daletu2e6e9ce88737ga2r7dkr7yc7dss7r6s85","author_url":"https://nostr.ae/npub1a3zpmn53lhv8jv7vjg3daletu2e6e9ce88737ga2r7dkr7yc7dss7r6s85","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-09-10\n📝 Original message:Hi,\n\nGiven today's presentation by Chris Jeffrey at the Breaking Bitcoin\nconference, and the subsequent discussion around responsible disclosure\nand industry practice, perhaps now would be a good time to discuss\n\"Bitcoin and CVEs\" which has gone unanswered for 6 months.\n\nhttps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013751.html\n\nTo quote:\n\n\"Are there are any vulnerabilities in Bitcoin which have been fixed but\nnot yet publicly disclosed?  Is the following list of Bitcoin CVEs\nup-to-date?\n\nhttps://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures\n\nThere have been no new CVEs posted for almost three years, except for\nCVE-2015-3641, but there appears to be no information publicly available\nfor that issue:\n\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3641\n\nIt would be of great benefit to end users if the community of clients\nand altcoins derived from Bitcoin Core could be patched for any known\nvulnerabilities.\n\nDoes anyone keep track of security related bugs and patches, where the\ndefect severity is similar to those found on the CVE list above?  If\nyes, can that list be shared with other developers?\"\n\nBest Regards,\nSimon"}