From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Subject: [9front] executable files in '#e'
Date: Wed, 10 Aug 2022 23:41:08 +0430 [thread overview]
Message-ID: <18521c30-7d04-2587-7cc7-7563d64489b7@riseup.net> (raw)
few days ago i noticed this behaviour on /env,
cpu% hold /env/test
cat: can't open /env/test: '/env/test' file does not exist
#!/bin/rc
echo hello world
cpu% ls -l /env/test
--rw-rw-rw- e 0 mkf mkf 27 Jul 18 2021 /env/test
cpu% /env/test
hello world
cpu%
it executes empty c programs as well, but i couldn't fit programs that
do something visable inside /env.
is it a security bug?
if yes, a possible attack could be creation of new variable and
executing it where we don't have file creation access.
reply other threads:[~2022-08-10 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=18521c30-7d04-2587-7cc7-7563d64489b7@riseup.net \
--to=mkf9@riseup.net \
--cc=9front@9front.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 NNTP newsgroup(s).