From: Yuri Khan <yuri.v.khan@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Jean Louis <bugs@gnu.support>, emacs-tangents@gnu.org
Subject: Re: 2023-02-27 Emacs news
Date: Wed, 1 Mar 2023 01:56:36 +0700 [thread overview]
Message-ID: <CAP_d_8W0zcJGp1kNiPH3Bb8quBmfAROskH0xe_0XYqPx97Yr6w@mail.gmail.com> (raw)
In-Reply-To: <88a8d27c-1eb3-b0f0-8929-027bbd024822@yandex.ru>
On Wed, 1 Mar 2023 at 01:08, Dmitry Gutov <dgutov@yandex.ru> wrote:
>
> On 28/02/2023 16:05, Yuri Khan wrote:
> > If you open a malicious source file in an editor, you don’t expect it
> > to execute any code written within, surely not before you press the
> > Run key. If opening a file for editing trashes your home directory,
> > it’s a bug and a vulnerability. If opening a file for editing causes
> > personal information to be sent outside, it’s a bug and a
> > vulnerability.
>
> Neither of that happened with the linked "vulnerability", though.
>
> It only worked if you pressed "C-c C-f" on a line that contained
> something like
>
> require '; rm -rf ~'
(ruby-find-library-file &optional FEATURE-NAME)
Visit a library file denoted by FEATURE-NAME.
FEATURE-NAME is a relative file name, file extension is optional.
[…] When called
interactively, defaults to the feature name in the ‘require’
or ‘gem’ statement around point.
So it’s not an auto-pwn but rather user-assisted, as in, *if* the
attacker can convince you to visit a malicious source file *and* do a
navigation command on a dangerously-looking import, *then* you’re
pwned? That significantly reduces the severity in my book.
next prev parent reply other threads:[~2023-02-28 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 0:16 2023-02-27 Emacs news Sacha Chua
2023-02-28 1:22 ` Emanuel Berg
2023-02-28 4:04 ` Jean Louis
2023-02-28 14:05 ` Yuri Khan
2023-02-28 18:08 ` Dmitry Gutov
2023-02-28 18:56 ` Yuri Khan [this message]
2023-02-28 19:34 ` Dmitry Gutov
2023-03-01 20:55 ` Emanuel Berg
2023-03-02 10:55 ` Pankaj Jangid
2023-03-03 19:11 ` Akib Azmain Turja
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=CAP_d_8W0zcJGp1kNiPH3Bb8quBmfAROskH0xe_0XYqPx97Yr6w@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=bugs@gnu.support \
--cc=dgutov@yandex.ru \
--cc=emacs-tangents@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.
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).