From: Dmitry Gutov <dgutov@yandex.ru>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Jean Louis <bugs@gnu.support>, emacs-tangents@gnu.org
Subject: Re: 2023-02-27 Emacs news
Date: Tue, 28 Feb 2023 21:34:10 +0200 [thread overview]
Message-ID: <18b496f7-f23c-67c0-8694-0a71af46848c@yandex.ru> (raw)
In-Reply-To: <CAP_d_8W0zcJGp1kNiPH3Bb8quBmfAROskH0xe_0XYqPx97Yr6w@mail.gmail.com>
On 28/02/2023 20:56, Yuri Khan wrote:
> 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.
Right.
The htmlfontify and etags vulns look a little more severe, though.
next prev parent reply other threads:[~2023-02-28 19:34 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
2023-02-28 19:34 ` Dmitry Gutov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18b496f7-f23c-67c0-8694-0a71af46848c@yandex.ru \
--to=dgutov@yandex.ru \
--cc=bugs@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=yuri.v.khan@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.