From: Yuri Khan <yuri.v.khan@gmail.com>
To: Jean Louis <bugs@gnu.support>
Cc: emacs-tangents@gnu.org
Subject: Re: 2023-02-27 Emacs news
Date: Tue, 28 Feb 2023 21:05:33 +0700 [thread overview]
Message-ID: <CAP_d_8XZ0GB_MVHyxyG68hEnD_SQtDDa99fdAo+_gfHD7ffa0g@mail.gmail.com> (raw)
In-Reply-To: <Y/19YVF/xXNt40eg@protected.localdomain>
On Tue, 28 Feb 2023 at 18:51, Jean Louis <bugs@gnu.support> wrote:
> But... it is source, one can put anything inside like
> (shell-command "sudo rm -rf /")
>
> Those "CVE" bugs are exaggerated.
>
> Like this one:
>
> https://security-tracker.debian.org/tracker/CVE-2022-48338
> "malicious Ruby source files may cause commands to be executed"
>
> But hey, any malicious source file may cause commands to be
> executed.
It is a question of expectations.
If you execute a malicious source file as a script, sure, you expect
it to be executed and you are ready for any damage it causes. There is
no vulnerability except in your own head.
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.
next prev parent reply other threads:[~2023-02-28 14:05 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 [this message]
2023-02-28 18:08 ` Dmitry Gutov
2023-02-28 18:56 ` Yuri Khan
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_8XZ0GB_MVHyxyG68hEnD_SQtDDa99fdAo+_gfHD7ffa0g@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=bugs@gnu.support \
--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).