From: Stefan Kangas <stefan@marxist.se>
To: adam plaice <plaice.adam+lists@gmail.com>
Cc: 37656@debbugs.gnu.org, Emacs developers <emacs-devel@gnu.org>
Subject: bug#37656: 27.0.50; Arbitrary code execution with special `mode:'
Date: Wed, 16 Oct 2019 00:55:08 +0200 [thread overview]
Message-ID: <CADwFkm=U1zfUsD4jTPj44mNvQX-h2gVrvXCkvjM5V7brhS71_Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnqfbsEEWkWMA2xnN1O+-JsTcCKrSYv0e3g1+jXrxRY5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
Stefan Kangas <stefan@marxist.se> writes:
> The below patch seems to fix it by disabling the feature it exploits.
Here is a more complete patch. Does it look like the right fix?
I think the relevant node in the documentation is:
(info "(emacs)Choosing Modes")
Best regards,
Stefan Kangas
[-- Attachment #2: 0001-Remove-support-for-more-than-one-mode-in-file-local-.patch --]
[-- Type: application/octet-stream, Size: 2032 bytes --]
From d640efe970ed1fdd5f1262d09bfd6d564c8e7f80 Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefankangas@gmail.com>
Date: Wed, 16 Oct 2019 00:44:56 +0200
Subject: [PATCH] Remove support for more than one mode in file local variables
* lisp/files.el (set-auto-mode): Remove support for specifying
more than one major mode in file local variables. (Bug#37656)
* etc/NEWS: Announce it.
---
etc/NEWS | 7 +++++++
lisp/files.el | 13 +++++++------
2 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/etc/NEWS b/etc/NEWS
index d06f0a5952..d0cec05143 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -197,6 +197,13 @@ the new version of the file again.)
\f
* Changes in Emacs 27.1
+---
+** File local variables can now specify only one major mode.
+Previously, it was possible to specify more than one major mode using
+file local variables. A security issue was discovered where an
+attacker could exploit this feature using a specially crafted file,
+which could lead to arbitrary code execution when the file was opened.
+
** emacsclient
+++
diff --git a/lisp/files.el b/lisp/files.el
index 40807617fa..41c1ba60ed 100644
--- a/lisp/files.el
+++ b/lisp/files.el
@@ -3066,12 +3066,13 @@ set-auto-mode
try-locals
(setq end (set-auto-mode-1))
(if (save-excursion (search-forward ":" end t))
- ;; Find all specifications for the `mode:' variable
- ;; and execute them left to right.
- (while (let ((case-fold-search t))
- (or (and (looking-at "mode:")
- (goto-char (match-end 0)))
- (re-search-forward "[ \t;]mode:" end t)))
+ ;; Find the specification of the `mode:' variable and
+ ;; execute it. We never want to execute more than one
+ ;; mode for security reasons. (Bug#37656)
+ (when (let ((case-fold-search t))
+ (or (and (looking-at "mode:")
+ (goto-char (match-end 0)))
+ (re-search-forward "[ \t;]mode:" end t)))
(skip-chars-forward " \t")
(let ((beg (point)))
(if (search-forward ";" end t)
--
2.23.0
next prev parent reply other threads:[~2019-10-15 22:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 21:05 bug#37656: 27.0.50; Arbitrary code execution with special `mode:' adam plaice
2019-10-15 22:23 ` Clément Pit-Claudel
2019-10-15 22:27 ` Stefan Kangas
2019-10-15 22:27 ` Stefan Kangas
2019-10-15 22:55 ` Stefan Kangas [this message]
2019-10-15 23:17 ` Stefan Kangas
2019-10-16 7:58 ` Eli Zaretskii
2019-10-16 11:51 ` Adam Plaice
2019-10-16 17:09 ` Eli Zaretskii
2019-10-16 19:09 ` Phil Sainty
2019-10-16 19:34 ` Eli Zaretskii
2019-10-16 21:02 ` Adam Plaice
2019-10-15 23:17 ` Stefan Kangas
2019-10-16 0:35 ` Adam Plaice
2019-10-16 7:57 ` Eli Zaretskii
2019-10-16 0:55 ` Phil Sainty
2019-10-16 0:55 ` Phil Sainty
2019-10-16 7:59 ` Eli Zaretskii
2019-10-16 6:43 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 8:48 bug#37656: 27.0.50; Opening file with specially crafted local variables can cause arbitrary code execution Inbox x adam plaice
2019-10-15 21:05 ` bug#37656: 27.0.50; Arbitrary code execution with special `mode:' adam plaice
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='CADwFkm=U1zfUsD4jTPj44mNvQX-h2gVrvXCkvjM5V7brhS71_Q@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=37656@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=plaice.adam+lists@gmail.com \
/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.