From: Peter Wang <novalazy@gmail.com>
To: notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: a DoS vulnerability associated with conflated Message-IDs?
Date: Mon, 29 Oct 2012 22:15:16 +1100 [thread overview]
Message-ID: <20121029221516.GB20292@hili.localdomain> (raw)
In-Reply-To: <87k42vrqve.fsf@pip.fifthhorseman.net>
On Thu, 08 Mar 2012 11:37:09 -0500, Daniel Kahn Gillmor <dkg@fifthhorseman.net> 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?
Peter
next prev parent reply other threads:[~2012-10-29 11:15 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 [this message]
2017-08-04 20:42 ` David Bremner
2017-08-04 22:15 ` Daniel Kahn Gillmor
2022-07-30 12:41 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121029221516.GB20292@hili.localdomain \
--to=novalazy@gmail.com \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).