From: Niklas Goegge <n.goeggi@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Public disclosure of three vulnerabilities affecting Bitcoin Core <v25.0
Date: Wed, 9 Oct 2024 12:30:16 -0700 (PDT) [thread overview]
Message-ID: <2df30c0a-3911-46ed-b8fc-d87528c68465n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]
Hi everyone,
Today we are releasing three security advisories for the Bitcoin Core
project. These vulnerabilities affect versions of Bitcoin Core before (and
not including) 25.0.
The details are available here:
-
https://bitcoincore.org/en/2024/10/08/disclose-mutated-blocks-hindering-propagation/
- https://bitcoincore.org/en/2024/10/08/disclose-large-inv-to-send/
- https://bitcoincore.org/en/2024/10/08/disclose-blocktxn-crash/
This is part of the gradual adoption by the project of a new vulnerability
disclosure policy. The policy is available at
https://bitcoincore.org/en/security-advisories/#policy. We will follow up
next month with vulnerabilities affecting Bitcoin Core versions before (and
not including) 26.0, if any.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/2df30c0a-3911-46ed-b8fc-d87528c68465n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1832 bytes --]
reply other threads:[~2024-10-09 21:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2df30c0a-3911-46ed-b8fc-d87528c68465n@googlegroups.com \
--to=n.goeggi@gmail.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox