gconf creates fork bomb using libproxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gconf (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gconf
I have maverick updated to last version.
Next I decide to update to Natty.
Upgrade process have been done with errors. I have found fork-bomb in system and what I done:
chmod a-x /usr/bin/
next upgrade continue, and after some amount of dpkg --configure -a the upgrade process have been done.
But when I enable execute_bits, fork bomb appear. Why?
gconf -> gio -> libgiolibproxy -> libproxy0.so -> config_gnome.so -> popen("gconf ...") -> sh -> gconf -> gio -> ...
See attached files: output of 'pstree -upal', gdb bt on process that begin that chain (it may be different process, but first items in stack are the same).
When I remove /usr/lib/
What the hell ?!
problem is easily reproductible on my computer ( by recovering /usr/lib/