unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: Fwd: Re: [oss-security] GNU Emacs 25.2 enriched text remote code execution
Date: Tue, 12 Sep 2017 11:18:12 -0700	[thread overview]
Message-ID: <f51f59e1-c074-5a58-6e9b-e81aa9721f49@cs.ucla.edu> (raw)
In-Reply-To: <87mv5zzt6n.fsf@mid.deneb.enyo.de>

I got the following response to the announcement on the oss-security 
mailing list. Question: what would cause the eval-after-load to be bypassed?


-------- Forwarded Message --------
Subject: 	Re: [oss-security] GNU Emacs 25.2 enriched text remote code 
execution
Date: 	Tue, 12 Sep 2017 20:08:00 +0200
From: 	Florian Weimer <fw@deneb.enyo.de>
To: 	Paul Eggert <eggert@cs.ucla.edu>
CC: 	oss-security@lists.openwall.com



* Paul Eggert:

> == Mitigation ==
>
> To work around the bug in unfixed versions of Emacs, put the following code in 
> your personal or site-wide Emacs init file (~/.emacs, ~/emacs.d/init.el, 
> site-start.el):
>
>    ;; Mitigate Bug#28350 (security) in Emacs 25.2 and earlier.
>    (eval-after-load "enriched"
>      '(defun enriched-decode-display-prop (start end &optional param)
>         (list start end)))

This does not override the function in all cases when enriched is
loaded.  Something like this would be more reliable, but it will of
course slow down the starting of Emacs:

(require 'enriched)
(defun enriched-decode-display-prop (start end &optional param)
   (list start end))




       reply	other threads:[~2017-09-12 18:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mv5zzt6n.fsf@mid.deneb.enyo.de>
2017-09-12 18:18 ` Paul Eggert [this message]
2017-09-13  5:07   ` Fwd: Re: [oss-security] GNU Emacs 25.2 enriched text remote code execution Kalle Olavi Niemitalo
2017-09-13  8:56     ` Paul Eggert
2017-09-13 12:19       ` Stefan Monnier
2017-09-13 14:46       ` Eli Zaretskii
2017-09-13 19:56         ` Paul Eggert

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=f51f59e1-c074-5a58-6e9b-e81aa9721f49@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).