From: Max Nikulin <manikulin@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>,
Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org, team@security.debian.org
Subject: Re: Reproducers for recent Emacs security issues
Date: Mon, 15 Apr 2024 18:20:12 +0700 [thread overview]
Message-ID: <d8c02c56-fef1-4c59-808e-ac1cf0bdd7c7@gmail.com> (raw)
In-Reply-To: <87y19fdklq.fsf@melete.silentflame.com>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
On 15/04/2024 16:46, Sean Whitton wrote:
>
> emacs -q
> M-x gnus-no-server
> Gf ~/tmp/mbox-with-the-msgs.mbox
> RET
I am not a Gnus user, but this time I have tried it. I have realized
that if there is an text/x-org attachment, even a purely innocent one,
then it is enough to have the following in the text/plain *body* to
trigger an attempt to download a remote file:
#+setupfile: http://localhost:8000/setup-1234567890.org
it happens when I open the message, the attachment remains closed.
I expect that message body should not affect attachment preview.
Emacs-28.2
[-- Attachment #2: innocent.org --]
[-- Type: text/org, Size: 9 bytes --]
Innocent
[-- Attachment #3: innocent-x.org --]
[-- Type: text/x-org, Size: 9 bytes --]
Innocent
next prev parent reply other threads:[~2024-04-15 11:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 3:23 Reproducers for recent Emacs security issues Sean Whitton
2024-04-14 4:41 ` Max Nikulin
2024-04-15 9:27 ` Sean Whitton
2024-04-15 9:32 ` Ihor Radchenko
2024-04-15 9:46 ` Sean Whitton
2024-04-15 10:09 ` Ihor Radchenko
2024-04-15 11:20 ` Max Nikulin [this message]
2024-04-15 12:00 ` Ihor Radchenko
2024-04-15 13:42 ` Andrew Cohen
2024-04-15 18:33 ` Florian Weimer
2024-04-15 23:30 ` Andrew Cohen
2024-04-16 4:35 ` Max Nikulin
2024-04-16 12:25 ` Eli Zaretskii
2024-04-16 13:23 ` Andrew Cohen
2024-04-17 14:31 ` Max Nikulin
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=d8c02c56-fef1-4c59-808e-ac1cf0bdd7c7@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
--cc=team@security.debian.org \
--cc=yantar92@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.