public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert L Waldrop <bob.waldrop@motorola.com>
To: martin.herfurt@trifinite.org, marcel@holtmann.org,
	bluez-users@lists.sourceforge.net
Subject: OPP and execl
Date: Thu, 28 Jul 2005 14:10:20 -0500	[thread overview]
Message-ID: <20050728191020.GD7483@urbana.css.mot.com> (raw)

Hi Everyone in BlueZ world,

I'm playing around with some OPP fun and was wondering whether anyone
had run into security issues using execl(...) from unistd.h.  I'm 
wondering if it is prone to a shell attack or buffer overrun if I
use it like this...

execl("/my/mycmd","mycmd","arg1","arg2");

Somehow the call forces arg1 (regardless of content, including special
characters like semi-colons) to be the argument of mycmd.  But I'm
curious if maybe there is a combination of characters that aren't 
escaped correctly and someone might be able to invoke a second command
or effect the kernel.  

Also wondering if I'm susceptible to someone passing a large string 
as arg1 if I open that up to the user.

If there are such problems, what is the typical answer to the need for
exec.

Muchas Gracias!

--bob w.

-- 
Robert Waldrop                  Motorola Personal Communications Sector
rwaldrop@urbana.css.mot.com     Urbana-Champaign Design Center
voice  217-384-8719             1800 South Oak Street
                                Champaign IL 61820

[X]  Motorola General Business Information
[ ]  Motorola Internal Use Only
[ ]  Motorola Confidential Proprietary

                 reply	other threads:[~2005-07-28 19:10 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=20050728191020.GD7483@urbana.css.mot.com \
    --to=bob.waldrop@motorola.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --cc=martin.herfurt@trifinite.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