public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Public disclosure of 1 vulnerability affecting Bitcoin Core <24.0.1
Date: Thu, 19 Sep 2024 05:15:30 +0000	[thread overview]
Message-ID: <WhFGS_EOQtdGWTKD1oqSujp1GW-v_ZUJemlNePPGaGBgzpmu6ThpqLwJpUVei85OiMu_xxjEzt_SeOWY7547C72BVISLENOd_qrdCwPajgk=@protonmail.com> (raw)

Hi everyone,

Today we are releasing 1 security advisory for the Bitcoin Core project. This vulnerability affects versions of Bitcoin Core before (and not including) 24.0.1.

The details for this vulnerability are available at https://bitcoincore.org/en/2024/09/18/disclose-headers-oom.

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) 25.0, if any.

Antoine Poinsot

-- 
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/WhFGS_EOQtdGWTKD1oqSujp1GW-v_ZUJemlNePPGaGBgzpmu6ThpqLwJpUVei85OiMu_xxjEzt_SeOWY7547C72BVISLENOd_qrdCwPajgk%3D%40protonmail.com.


             reply	other threads:[~2024-09-19  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19  5:15 'Antoine Poinsot' via Bitcoin Development Mailing List [this message]
2024-09-19  8:12 ` [bitcoindev] Re: Public disclosure of 1 vulnerability affecting Bitcoin Core <24.0.1 Antoine Riard

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='WhFGS_EOQtdGWTKD1oqSujp1GW-v_ZUJemlNePPGaGBgzpmu6ThpqLwJpUVei85OiMu_xxjEzt_SeOWY7547C72BVISLENOd_qrdCwPajgk=@protonmail.com' \
    --to=bitcoindev@googlegroups.com \
    --cc=darosior@protonmail.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