From: Paul Eggert <eggert@cs.ucla.edu>
To: "Charles A. Roelli" <charles@aurox.ch>
Cc: larsi@gnus.org, 28350@debbugs.gnu.org
Subject: bug#28350: enriched.el code execution
Date: Sun, 10 Sep 2017 14:46:59 -0700 [thread overview]
Message-ID: <89bf7f23-d065-572c-ad54-bce7cb9a02e7@cs.ucla.edu> (raw)
In-Reply-To: <m24lsa9yga.fsf@aurox.ch>
Charles A. Roelli wrote:
> Do we know that "x-color" and/or "x-bg-color" are vulnerable to a
> similar misuse as "x-display"? If not, I can still re-add them at a
> later time.
Eli asked the same question privately. I don't know the code myself; perhaps
Lars could say.
>> + (provide 'enriched)
>> + (defun enriched-mode (&optional arg))
>> + (defun enriched-decode (from to))
>
> This fix is very safe, at the cost of disabling Enriched mode. Could
> we do any better? I had suggested the following (in
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28350#16):
>
> (eval-after-load "enriched"
> '(defun enriched-decode-display-prop (start end &optional param)
> (list start end)))
>
> But it may not work in Emacs earlier than 23 (I can't test it).
It should work, since eval-after-load predates Emacs 19.29. Though it assumes
that x-display is the only problem here.
next prev parent reply other threads:[~2017-09-10 21:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 19:24 bug#28350: enriched.el code execution Charles A. Roelli
2017-09-06 19:25 ` Charles A. Roelli
2017-09-07 2:34 ` Eli Zaretskii
2017-09-09 12:23 ` Charles A. Roelli
2017-09-09 13:45 ` Eli Zaretskii
2017-09-09 15:57 ` Charles A. Roelli
2017-09-09 16:55 ` Eli Zaretskii
2017-09-09 20:37 ` Charles A. Roelli
2017-09-10 17:01 ` Eli Zaretskii
2017-09-11 16:32 ` Glenn Morris
2017-09-11 17:01 ` Eli Zaretskii
2017-09-09 22:43 ` Paul Eggert
2017-09-10 18:54 ` Charles A. Roelli
2017-09-10 21:46 ` Paul Eggert [this message]
2017-09-11 2:39 ` Eli Zaretskii
2017-09-11 14:22 ` Eli Zaretskii
2017-09-11 15:18 ` Eli Zaretskii
2017-09-11 18:44 ` Charles A. Roelli
2017-09-11 19:07 ` Eli Zaretskii
2017-09-16 9:48 ` Eli Zaretskii
2017-09-11 15:33 ` Glenn Morris
2017-09-11 16:38 ` Paul Eggert
2017-09-11 21:16 ` Glenn Morris
2017-09-12 19:59 ` 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=89bf7f23-d065-572c-ad54-bce7cb9a02e7@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=28350@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=larsi@gnus.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).