Live data from Hacker News

Developers fix multitude of vulnerabilities in Apache HTTP Server

portswigger.net

31–40 of 115 posts

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#31
post #3

On Debian 10, "apt update && apt upgrade" says all packages are up to date. Did the fixes not land in Debian yet?

>All five flaws are resolved with HTTP Server 2.4.49. The WSL version of Ubuntu is reporting 2.4.41 for me still. I don't know about the real version.

WSL ubuntu uses the same repos as regular ubuntu so they should be in sync

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#33
post #4

Anybody still using Apache?

Note: several folks have pointed out that I was totally wrong about Caddy. Sorry! I should look at it again before I spout off any more opinions about it.

Unlike nginx or Caddy^H^H^H^H^H, the Apache design and community encouraged writing modules (roughly akin to "middleware" in the modern server-side web stack) that hooked directly into the web server, rather than just using it as a static host + L7 proxy.

Furthermore, these modules could themselves expose language-specific APIs; ergo `mod_perl` and its ilk, which provide a bunch of useful building blocks for a full-stack webapp but are entirely specific to Apache's module API (vs. something more standard like FCGI, WSGI, etc.)

I've worked at some shops with heavy investments in Apache-based application servers and the cost of moving away from HTTPD modules and towards a more standalone, Apache-free implementation was generally quite high. Usually you need some other forcing function (rewrite in a new language, microservice decomposition, etc.) to justify the investment.

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#34

Earlier quoted context omitted.

What's wrong with Apache? (honest question)

I was looking for a pre-hardened httpd just for serving static html files, is there one?

Probably not the answer you want to hear... But I push that stuff to AWS S3 website and put a CDN in front for SSL... that's my solution for "easy secure static site" when I don't want to invest more than an hour or so a year on the infrastructure... But obviously that's not for everyone.

Edit: specific to your request, I would probably set up a container pointing to the latest apache build, and write a script to pull the latest image then roll over the container... Don't need to wait for your OS of choice to have the fixed versions... Your never more than a day behind

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#35
post #3

On Debian 10, "apt update && apt upgrade" says all packages are up to date. Did the fixes not land in Debian yet?

Quite often there are many vulnerabilities with no ‘fixed-in’ version (as it’s not yet fixed) and this can be for some time.

https://security-tracker.debian.org/tracker/status/release/s... is one place to look through in the past I think there was a better link I used to use to find all vulnerable packages which were awaiting a fix - but I can’t seem to find it now.

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#36

Earlier quoted context omitted.

What's wrong with Apache? (honest question)

I was looking for a pre-hardened httpd just for serving static html files, is there one?

https://github.com/emikulic/darkhttpd

darkhttpd is an option

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#38

This was an interesting security patch that marked the first time in my memory that updating Apache led to an immediate regression. A few hours after taking this upgrade many systems experienced such strange timeout errors. Connections were low and couldn't pinpoint the misleading behavior that looked like a slowloris attack, with no connections. Half a day later with no resolution in research a new patch [1] was ava…

Those who can't program, go to security research.

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#39

It's called Apache HTTP server because it's A Patchy HTTP Server. https://www.mail-archive.com/fedora-list@redhat.com/msg06924... >On Jul 16, 2008, Les Mikesell wrote: >> Alexandre Oliva wrote: >> Apache wasn't the original name. >It was and it wasn't. It was indeed a bunch of patches on top of the (also younger) NCSA http server. That's where "a patchy http server" came from. But that was '90s already, some ten year…

Every day someone is born who has never seen The Flintstones

Re: Developers fix multitude of vulnerabilities in Apache HTTP Server

#40

It's called Apache HTTP server because it's A Patchy HTTP Server. https://www.mail-archive.com/fedora-list@redhat.com/msg06924... >On Jul 16, 2008, Les Mikesell wrote: >> Alexandre Oliva wrote: >> Apache wasn't the original name. >It was and it wasn't. It was indeed a bunch of patches on top of the (also younger) NCSA http server. That's where "a patchy http server" came from. But that was '90s already, some ten year…

Every day someone is born who has never seen The Flintstones

Everyday someone is born who hasn't seen everything, or anything.
Post reply on HN