all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Christopher Howard <christopher@librehacker.com>
Cc: Emacs Devel Mailing List <emacs-devel@gnu.org>
Subject: Re: Emacs Arbitrary Code Execution and How to Avoid It
Date: Wed, 4 Dec 2024 12:39:00 +0300	[thread overview]
Message-ID: <Z1AjNPVdoP-UtE3U@lco2> (raw)
In-Reply-To: <878qswfya2.fsf@librehacker.com>

* Christopher Howard <christopher@librehacker.com> [2024-12-03 20:56]:
> Hi, I read the interesting write up here:
> 
> https://eshelyaron.com/posts/2024-11-27-emacs-aritrary-code-execution-and-how-to-avoid-it.html
> 
> I wasn't terribly worried about this, as I don't *automatically* activate Flymake or Flycheck. But the article did mention that "code completion runs arbitrary code", and I was wondering more about that. I do not currently use Completion Preview mode. I have used Company in the past but company-mode is not currently activated. So, if I am just viewing an elisp file, i.e., not typing anything it in, nor running dabbrev commands, is there any danger? Should I setup Emacs to, by default, open all elisp files in View Mode?
> 
> Regarding dabbrev, I know dabbrev can search all buffers but I don't know if it does any macro expansion.
> 
> I was going to e-mail the author of the post, but cloudflare won't let me see his e-mail address.

In every programming language it is possible to obscure the code and execute arbitrary code.

I do not see it as special security issue, it is common, known.

-- 
Jean Louis



  parent reply	other threads:[~2024-12-04  9:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 17:53 Emacs Arbitrary Code Execution and How to Avoid It Christopher Howard
2024-12-03 19:20 ` Gerd Möllmann
2024-12-03 20:25   ` Eshel Yaron
2024-12-08  5:10     ` Richard Stallman
2024-12-06  4:47   ` Richard Stallman
2024-12-06  8:30     ` Eli Zaretskii
2024-12-09  4:57       ` Richard Stallman
2024-12-09 13:59         ` Eli Zaretskii
2024-12-04  9:39 ` Jean Louis [this message]
2024-12-04 15:04   ` Steven Allen
2024-12-04 17:02     ` Jean Louis
2024-12-04 17:23       ` Christopher Howard
2024-12-07  4:23       ` Richard Stallman
2024-12-10 18:03         ` Daniel Radetsky
2024-12-11  8:35           ` Eshel Yaron
2024-12-11  9:25             ` Jean Louis
2024-12-11  9:37               ` Daniel Radetsky
2024-12-11 10:38                 ` Jean Louis
2024-12-11 10:42                   ` tomas
2024-12-11 12:50                   ` Daniel Radetsky
2024-12-11 13:10                     ` tomas
2024-12-12  4:48           ` Richard Stallman
2024-12-12  7:39             ` Jean Louis
2024-12-06  4:47 ` Richard Stallman
2024-12-06  5:30   ` Jim Porter
2024-12-06  8:32     ` Eli Zaretskii
2024-12-06  8:29   ` Eli Zaretskii
2024-12-06 16:51   ` Philip Kaludercic
2024-12-08  5:15     ` Richard Stallman

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=Z1AjNPVdoP-UtE3U@lco2 \
    --to=bugs@gnu.support \
    --cc=christopher@librehacker.com \
    --cc=emacs-devel@gnu.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 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.