Apache 1.3.26

:hiphop: if your cpu is invaded logout:hiphop:

I'm currently running Apache1.3.26 an was thinking of using it as a web server.

Is there any weakness in it or should I upgrade . :o

Hmm...something strikes me as odd about this, you are currently running apache 1.3.26 and you are just now thinking of running it as a web server? If you aren't using a service you should turn it off, the more things you are running the more potential ways in for someone else. I have a few misgivings about this, but here is the answer:

It is usually good to check the vendor's web site to find information like this, so :
www.apache.org

A good place to look for vendor version/vuln lists is on www.securityfocus.com, look around for apache, it is very good about discussing the nature of problems and what can be done to fix them.

/nebulus

Thanks for that advise,

Latest release (of httpd) from the apache group is 1.3.27, but some vendors/distros are not there yet.

1.3.27 is supposed to fix security flaws, but I'm uncertain of the implications of the fixes: I'm thinking of OpenBSD that doesn't even address what's refered in the 1.3.27 fix... Is it that the flaws fixed in 1.3.27 are platform dependent and openbsd isn't vulnerable? Anybody has info about that?

Ammo

There are many possibilities, would require reading the discussion a little bit, but here goes for everything prior to 1.3.27 for this month for strictly apache (not modssl, apachessl, tomcat, etc ), as with most vulns, it depends on platform:

http://online.securityfocus.com/bid/5996
http://online.securityfocus.com/bid/5995
http://online.securityfocus.com/bid/5847
http://online.securityfocus.com/bid/5884 <-- seems to effect most vendors

The new version more than likely addresses these problems.

http://httpd.apache.org/

Also explicitly lists several CAN's that are addressed as well.

Happy reading,

/nebulus

EDIT: CVE--_>CAN