From: "David A. Harding" <dave@dtrt•org>
To: Antoine Riard <antoine.riard@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Full-Disclosure: CVE-2025-27586 "No Santa Claus under the Lightning Sun"
Date: Tue, 17 Jun 2025 16:16:56 -1000 [thread overview]
Message-ID: <1b4a4871c6531da5a7fdcf67cd218848@dtrt.org> (raw)
In-Reply-To: <fe76185f-8d9c-41b2-ab15-117d7787a204n@googlegroups.com>
On 2025-06-12 09:03, Antoine Riard wrote:
> This class of attacks dubbed "fee-bumping reserves exhaustion attacks"
> [...]
> ## Timeline
>
> - 2022-07-11: Report of the finding to XXX, Bastien Teinturier
> (Eclair), Lisa Neigut
Hi Antoine,
I read your post twice but everything in it seems obvious. What am I
missing? It's obvious that (1) exogenous fee bumping requires keeping
an independent reserve of sufficient funds and (2) that the amount of
the reserve can vary depending on transaction size and prevalent
feerates. The earliest description of that problem I found is from more
than a year before your report (
https://github.com/lightningnetwork/lnd/pull/4908 ), but I suspect I
could find other even earlier discussion if I looked harder.
Is there more to this vulnerability report that I'm missing?
Thanks,
-Dave
--
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 visit https://groups.google.com/d/msgid/bitcoindev/1b4a4871c6531da5a7fdcf67cd218848%40dtrt.org.
prev parent reply other threads:[~2025-06-18 3:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 19:03 Antoine Riard
2025-06-18 2:16 ` David A. Harding [this message]
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=1b4a4871c6531da5a7fdcf67cd218848@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=antoine.riard@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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