From: Noam Postavsky <npostavs@gmail.com>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: 30912@debbugs.gnu.org
Subject: bug#30912: emacs as a route to privilege escalation
Date: Thu, 22 Mar 2018 20:05:01 -0400 [thread overview]
Message-ID: <87lgejslle.fsf@gmail.com> (raw)
In-Reply-To: <CMM.0.95.0.1521762082.beebe@gamma.math.utah.edu> (Nelson H. F. Beebe's message of "Thu, 22 Mar 2018 17:41:22 -0600")
forcemerge 28618 30912
quit
"Nelson H. F. Beebe" <beebe@math.utah.edu> writes:
> The SANS security list today carried a pointer to this Web site:
>
> Abusing Text Editors with Third-party Plugins
> March 15, 2018
> Dor Azouri
> https://safebreach.com/Post/Abusing-Text-Editors-with-Third-party-Plugins
>
> It links to an 11-page report of the same title at
>
> https://go.safebreach.com/rs/535-IXZ-934/images/Abusing_Text_Editors.pdf
>
> Do emacs developers wish to respond to the security attacks described
> there?
Dor already brought this up in Bug#28618. As Glenn said:
If an attacker has [compromised] a user account that can run "sudo arbitrary
command", then that's just the same as having compromised the root
account, and so worrying about this on the individual application level
doesn't seem to make sense. Eg they could replace "sudo" with a keylogger.
Note that the problem could be "fixed" by setting
Defaults always_set_home
in /etc/sudoers (Debian has this setting by default), but that won't
help with the sudo-is-a-key-logger problem.
prev parent reply other threads:[~2018-03-23 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 23:41 bug#30912: emacs as a route to privilege escalation Nelson H. F. Beebe
2018-03-22 23:57 ` Lars Ingebrigtsen
2018-03-24 18:15 ` Richard Stallman
2018-03-23 0:05 ` Noam Postavsky [this message]
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=87lgejslle.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=30912@debbugs.gnu.org \
--cc=beebe@math.utah.edu \
/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).