emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rafael Ramirez Morales <rafael.ramirezmorales@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 48676@debbugs.gnu.org
Subject: bug#48676: Arbitrary code execution in Org export macros
Date: Thu, 27 May 2021 09:02:20 +0200	[thread overview]
Message-ID: <CAL1NY7bbWcCX7Ni1t+LcxL9_jdBmCgKkfj9u=xUqxaLoxJkJig@mail.gmail.com> (raw)
In-Reply-To: <2nk0nl7asb.fsf@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

Just a couple of questions:
who is the owner of the HELLO file?
who is the owner of the "touch" process?

Is the owner the unprivileged user or the "emacs" system?


On Wed, 26 May 2021 at 17:53, Glenn Morris <rgm@gnu.org> wrote:

> Package: emacs,org-mode
> Version: 28.0.50
> Severity: important
> Tags: security
> emacs -Q hello.org, where hello.org contains:
> #+macro: hello (eval (shell-command-to-string "touch /tmp/HELLO"))
> Hello. {{{hello}}}
> Then:
> M-x org-export-dispatch
> t A
> -> now /tmp/HELLO exist, with no prompting.
> This seems contrary to normal Emacs practice for risky local variables,
> and to the section "Code Evaluation and Security Issues" in the Org manual
> (which does not mention macros).

[-- Attachment #2: Type: text/html, Size: 1370 bytes --]

  parent reply	other threads:[~2021-05-27 12:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26 15:52 Glenn Morris
2021-05-26 17:07 ` Timothy
2021-05-26 18:00   ` Tom Gillespie
2021-05-26 23:01 ` Tim Cross
2021-05-27  2:54 ` Greg Minshall
2021-05-27  7:02 ` Rafael Ramirez Morales [this message]
2021-05-27 12:55   ` Tim Cross
2021-05-27 13:35     ` Rafael Ramirez Morales

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL1NY7bbWcCX7Ni1t+LcxL9_jdBmCgKkfj9u=xUqxaLoxJkJig@mail.gmail.com' \
    --to=rafael.ramirezmorales@gmail.com \
    --cc=48676@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    --subject='Re: bug#48676: Arbitrary code execution in Org export macros' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).