NOTE: Assigned to apache component; no htdig component.
A new potentially nasty risk has surfaced.
It is a new remotely accessible cgi binary.
It is called "htsearch" and it is a 350kb binary.
This risk is present with a full install and with apache running.
Note that the other two cgi binaries in a full install are not
Can we please make this new cgi binary inaccessible by
default, like we did with "nut-cgi"!
Maybe split the htdig package. Most people will only install it since it is a
KDE. So putting the cgi file into a separate package would resolve this problem.
I've split the htdig package - the problem remains on a typical newbie's
"Everything" install, though.
Alternatives (I don't really like any of them):
- chmod 0644 the CGI. Gets rid of the possible security leak, but makes it
harder to use the
functionality if it's wanted
- Change the default httpd.conf not to start any CGIs (same problems as with #1,
This defect is considered MUST-FIX for Florence Gold release
After discussing it with Bero i think we should stick with the current solution.
The thing is that after even a 'Everything' installation apache is not turned on
(like hardly any other daemon), leaving the system in a secure state.
If someone now activates apache he/she has to be aware that after a 'Everything'
installation quite a few packages get installed and some most likely related to
apache, so it's now in the responsibility of the user to make sure he/she only
has the packages installed he/she really wants.
And with a normal installation the htdig-web won't be installed and therefore
even apache will be after activation remain as secure as it always was ;).
And installing the htdig-web package and having the htsearch not being
executable is extremely pointless. It's like installing netscape without
execution permission and then expecting the user to active this insecure web
I'd call it fixed this way. Other suggestions are as always welcome...
Read ya, Phil