Skip to content

Conversation

@bitschmidty
Copy link
Contributor

@bitschmidty bitschmidty commented Oct 27, 2025

@bitschmidty bitschmidty self-assigned this Oct 27, 2025
@TumaBitcoiner
Copy link
Contributor

I will take a look at this:

Bitcoin Core security advisories https://groups.google.com/g/bitcoindev/c/sBpCgS_yGws

Copy link
Contributor Author

@bitschmidty bitschmidty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trailing spaces build fixup for @TumaBitcoiner section


- **Disclosure of four low severity vulnerabilities in Bitcoin Core:**
Antoine Poinsot recently [posted][poinsot disc] to the Bitcoin Development Mailing List four Bitcoin Core security advisories for low severity vulnerabilities that were fixed in [Bitcoin Core 30.0][]. According to the [disclosure policy][disc pol], a low severity vulnerability is disclosed two weeks after the release of a major version containing the fix.
The four disclosed vulnerabilities are the following:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was intended to be on a new line

- [CVE-2025-46597][]: Highly unlikely remote crash on 32-bit systems. This bug may cause a node to crash when receiving a pathological block, in a rare edge case.

- [CVE-2025-46598][]: CPU DoS from unconfirmed transaction processing. This bug would cause resource exhaustion when processing an unconfirmed transaction.
Patches for the first three vulnerabilities have been included also in [Bitcoin Core 29.1][] and later minor releases.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This, too, should be on a new line.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TumaBitcoiner can you update accordingly? Also, you can run make production to run the same sort of checks done here separate from make preview

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I'll do it.
Is it possible to run a similar make production code from Docker? I'm having issues running the needed version of Ruby on the latest Debian.

Copy link
Contributor Author

@bitschmidty bitschmidty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feedback for @TumaBitcoiner

weeks after the release of a major version containing the fix. The four
disclosed vulnerabilities are the following:

- [CVE-2025-54604][]: Disk filling from spoofed self connections. This bug
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im not strong on it, but we could follow the format of previous disclosures here in terms of bullets: https://bitcoinops.org/en/newsletters/2024/07/05/#disclosure-of-vulnerabilities-affecting-bitcoin-core-versions-before-0-21-0

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I'll follow the format of previous newsletters!

Antoine Poinsot recently [posted][poinsot disc] to the Bitcoin Development
Mailing List four Bitcoin Core security advisories for low severity
vulnerabilities that were fixed in [Bitcoin Core 30.0][]. According to the
[disclosure policy][disc pol], a low severity vulnerability is disclosed two
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alternative link could be our coverage of that policy in the newsletter previously

Copy link
Contributor Author

@bitschmidty bitschmidty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feedback for @Gustavojfe


- **Disclosure of four low severity vulnerabilities in Bitcoin Core:**
Antoine Poinsot recently [posted][poinsot disc] to the Bitcoin Development
Mailing List four Bitcoin Core security advisories for low severity
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Mailing List four Bitcoin Core security advisories for low severity
Mailing List four Bitcoin Core security advisories for low-severity

Copy link
Contributor

@kevkevinpal kevkevinpal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feedback for @TumaBitcoiner
Added some suggestions to give credit to whoever discovered the CVE's and merged the mitigations.

Feel free to add or leave as is

weeks after the release of a major version containing the fix. The four
disclosed vulnerabilities are the following:

- [CVE-2025-54604][]: Disk filling from spoofed self connections. This bug
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes sense to work in credit to whoever found the venuralbility if you can.

In this case, Niklas Goegge and both Eugene Siegel and Niklas Goegge worked on the mitigation

Maybe adding
The vulnerability was disclosed responsibly by Niklas Goegge in March 2022. Eugene Siegel and Niklas Goegge merged a mitigation in July 2025.

- [CVE-2025-46598][]: CPU DoS from unconfirmed transaction processing. This
bug would cause resource exhaustion when processing an unconfirmed
transaction. Patches for the first three vulnerabilities have been included
also in [Bitcoin Core 29.1][] and later minor releases.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
also in [Bitcoin Core 29.1][] and later minor releases.
edge case. This bug was reported to the mailing list by Antoine Poinsot in April 2025. Pieter Wuille, Anthony Towns, and Antoine Poinsot implemented and merged the mitigation in August 2025.

@bitschmidty bitschmidty force-pushed the 2025-10-31-newsletter branch from 21740e5 to e3ccc55 Compare October 31, 2025 11:45
@bitschmidty
Copy link
Contributor Author

Force pushed some updates (I had begun making final changes already but took in changes recently made by @TumaBitcoiner). Added topic entries for the disclosures topic related to the news item.

@bitschmidty bitschmidty force-pushed the 2025-10-31-newsletter branch from e3ccc55 to a722c9e Compare October 31, 2025 12:56
@bitschmidty bitschmidty force-pushed the 2025-10-31-newsletter branch 4 times, most recently from 5ac8daf to a266742 Compare October 31, 2025 13:15
@bitschmidty bitschmidty force-pushed the 2025-10-31-newsletter branch from a266742 to 7d5f57c Compare October 31, 2025 13:27
@bitschmidty bitschmidty merged commit b378c53 into bitcoinops:master Oct 31, 2025
1 of 2 checks passed
@bitschmidty
Copy link
Contributor Author

Noticed the notable code segment still had an errant PR, so removed it. Tweaked the topic entries and the lede.

Squashed.

Thank you @TumaBitcoiner and @Gustavojfe for authoring this week. Thanks to @LarryRuane for the review and @kevkevinpal for the review and suggestions in the news section. 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants