Bug 15211 - connection names not checked for shell escapes
connection names not checked for shell escapes
Product: Red Hat Linux
Classification: Retired
Component: rp3 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
: Security
: 16488 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-08-03 03:19 EDT by o.schnapauff
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-08-03 03:19:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description o.schnapauff 2000-08-03 03:19:19 EDT
Maybe Security problem:

rp3 / rp3-config doesnt properly check the buffer contents for special characters. Result: Anyone that can start rp3-config or rename a 
connection name  can run an arbitrary command as root.

As you seem to need the root pass to start rp3-config things arent too terrible, but this could still have bad side effects.

Do this: start rp3-config, as connection name use <something>&<command>

then try to start or stop that connection with rp3. <command> will be run as root. Happened originally when my connection was called "at&t"...

I suggest this should be fixed if there is any way a user or skript could ever provide a provider name to rp3.


Comment 1 Nalin Dahyabhai 2000-08-03 11:10:04 EDT
This will be fixed in CVS and in rp3-1.1.2-5 and later.  All shell
metacharacters will now be quoted.
Comment 2 Nalin Dahyabhai 2000-08-19 23:55:35 EDT
*** Bug 16488 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.