unsafe use of dlopen(3)

Bug #1119985 reported by Seth Arnold
256
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vde2 (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

TRY_DLOPEN("%s%s", modname, MODULES_EXT);
TRY_DLOPEN("%s%s/%s", homedir, USER_PLUGINS_DIR, modname);
TRY_DLOPEN("%s%s/%s%s", homedir, USER_PLUGINS_DIR, modname, MODULES_EXT);
TRY_DLOPEN("%s%s", PLUGINS_DIR, modname);
TRY_DLOPEN("%s/%s%s", PLUGINS_DIR, modname, MODULES_EXT);

It is generally considered poor form to load executable content from the current working directory (as this code does if getenv("HOME") fails), and loading code from a home directory seems suspect to me. However, I do not know the design well enough to make this determination myself.

Please consider if this is unsafe or intentional. If it is intentional, make sure that the documentation accurately reflects the risk of allowing executable content to exist in current working directories or home directories.

Revision history for this message
Seth Arnold (seth-arnold) wrote :
Changed in vde2 (Ubuntu):
status: New → Triaged
information type: Private Security → Public Security
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.