The latest PHP worm (lupii) attacks systems that are vulnerable to a remote code execution hole in PEAR::XMLRPC (or phpxmlrpc). It can only propagate on systems whose administrators have neglected to update PHP (or PEAR) in the last 3 months. Those three months have seen 4 PHP version bumps alone in the PHP4 tree, and anyone who hasn’t brought his PHP up to scale is probably a moron anyway.
However, at least for PEAR, this might be easily fixable. What if the PEAR project would introduce a flag for packets, say, “-security” and modify the PEAR installer accordingly. That flag should only be used for pure security fixes, without feature or BC breakage, so that it won’t break anything at all (apart from the exploits).
A new action for the installer, say, “pear upgrade-security” could then be introduced. It would enable admins to run pear in a nightly cronjob, only fetching security fixes and installing them in a fully automated way.
Comments, everyone - is that feasible? Does a similar concept already exist?