From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: lx@shellcodes.org, 59817@debbugs.gnu.org
Subject: bug#59817: [PATCH] Fix etags local command injection vulnerability
Date: Sun, 04 Dec 2022 19:04:15 +0200 [thread overview]
Message-ID: <83lenn9k34.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmmGvC_Q+e=FFRN1jBtOycLs0iXO3KanU8fTBwpff0WJJw@mail.gmail.com> (message from Stefan Kangas on Sun, 4 Dec 2022 08:27:14 -0800)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 4 Dec 2022 08:27:14 -0800
> Cc: 59817@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, but no, thanks. This cure is worse than the disease. Let's please
> > find simpler, more robust solutions. It TMPDIR is a problem, let's use a
> > file whose name is hard-coded in the etags.c source, or quote the name when
> > we pass it to the shell. If we suspect someone could disguise shell
> > commands as file names, let's quote the file names we pass to the shell with
> > '...' to prevent that. Etc. etc. -- let's use simple solutions that don't
> > drastically change the code.
>
> With single quotes, every single quote character also needs to be quoted
> so you can't just use a file named "';rm -rf $HOME;'".
Yes. But still, doing so is hardly rocket science, and it leaves the
general design of etags.c intact.
> The safest option is to just not call system, of course.
I'd rather not go there unless it was really necessary.
next prev parent reply other threads:[~2022-12-04 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 13:51 bug#59817: [PATCH] Fix etags local command injection vulnerability lux
2022-12-04 14:39 ` Eli Zaretskii
2022-12-04 16:27 ` Stefan Kangas
2022-12-04 17:04 ` Eli Zaretskii [this message]
[not found] ` <tencent_2F6B5EEED2E485C363837738F5661E6AB009@qq.com>
2022-12-05 12:34 ` Eli Zaretskii
2022-12-06 7:48 ` lux
2022-12-06 12:55 ` Eli Zaretskii
2022-12-06 13:11 ` lux
2022-12-06 14:52 ` Eli Zaretskii
2022-12-06 15:05 ` Francesco Potortì
2022-12-06 15:19 ` Francesco Potortì
2022-12-06 15:49 ` lux
2022-12-06 16:14 ` Eli Zaretskii
2022-12-06 13:05 ` Andreas Schwab
2022-12-06 14:33 ` Eli Zaretskii
2022-12-05 0:58 ` lux
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=83lenn9k34.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59817@debbugs.gnu.org \
--cc=lx@shellcodes.org \
--cc=stefankangas@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 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).