From: David Bremner <firstname.lastname@example.org>
To: Daniel Kahn Gillmor <email@example.com>,
Peter Wang <firstname.lastname@example.org>,
notmuch mailing list <email@example.com>
Subject: Re: a DoS vulnerability associated with conflated Message-IDs?
Date: Sat, 30 Jul 2022 09:41:41 -0300 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Daniel Kahn Gillmor <email@example.com> writes:
> On Fri 2017-08-04 16:42:54 -0400, David Bremner wrote:
>> Peter Wang <firstname.lastname@example.org> writes:
>>> On Thu, 08 Mar 2012 11:37:09 -0500, Daniel Kahn Gillmor <email@example.com> wrote:
>>>> notmuch currently treats all messages with the same Message-ID as
>>>> the same message. I think this could be a vulnerability :(
>>>> If two messages have the same Message-ID, is there a guarantee of which
>>>> of these messages will be produced during a notmuch show?
>>>> Either way, it seems to create a potential DoS attack on notmuch users.
>>> Yesterday I was expecting a confirmation message which, seemingly, never
>>> came. It turns out my maildir already contained a message from the
>>> same system. From three years ago. With the same Message-ID.
>>> Malice has nothing on incompetence.
>>> Could we distinguish messages with identical Message-IDs based on
>>> some header fields, e.g. Date, From?
>> I wouldn't say this problem is fixed, but we are making some
>> progress. In master all copies of the file are now indexed. It still
>> needs various UI work before we can consider the problem really fixed,
>> but it is now technically possible to detect such an attack (since the
>> "good terms" are also indexed).
> otoh, we now enable some additional (perhaps weirder) attacks, like:
> * i can make someone else's mail show up in your mailbox with a search
> term of my choosing by sending you a new mail co-opting their
> we definitely need some UI for dealing with this, and perhaps some
> explicit de-duping logic or maintenance scripts would be useful too.
There is now a simple UI for dealing with duplicate messages in the
emacs UI (as of commit 1ef7c75111b84ea19af3186ddc12f2ba434c93de, which
should be part of 0.37).
prev parent reply other threads:[~2022-07-30 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 16:37 a DoS vulnerability associated with conflated Message-IDs? Daniel Kahn Gillmor
2012-03-08 17:04 ` James Vasile
2012-03-08 17:16 ` Daniel Kahn Gillmor
2012-03-08 17:38 ` Jeremy Nickurak
2012-03-10 17:38 ` Tom Prince
2012-10-29 11:15 ` Peter Wang
2017-08-04 20:42 ` David Bremner
2017-08-04 22:15 ` Daniel Kahn Gillmor
2022-07-30 12:41 ` David Bremner [this message]
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:
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).