public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] apache: Update to 2.4.49
Date: Sat, 18 Sep 2021 16:08:42 +0000	[thread overview]
Message-ID: <4aaca06f-c794-c287-aa50-c5da0bfbc51d@ipfire.org> (raw)
In-Reply-To: <20210918134743.8100-1-matthias.fischer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Hi Matthias,

thanks for submitting this.

Skimming through https://httpd.apache.org/security/vulnerabilities_24.html, I think IPFire is
vulnerable to CVE-2021-34798 ("moderate: NULL pointer dereference in httpd core") only. CVE-2021-39275
would require 3rd party modules, which we don't use, and the rest applies to mod_proxy, which
we don't use either IMHO.

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

Thanks, and best regards,
Peter Müller


> For details see:
> https://dlcdn.apache.org//httpd/CHANGES_2.4.49
> 
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
>   lfs/apache2 | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/apache2 b/lfs/apache2
> index ff9de7eb7..e63489e8f 100644
> --- a/lfs/apache2
> +++ b/lfs/apache2
> @@ -25,7 +25,7 @@
>   
>   include Config
>   
> -VER        = 2.4.48
> +VER        = 2.4.49
>   
>   THISAPP    = httpd-$(VER)
>   DL_FILE    = $(THISAPP).tar.bz2
> @@ -45,7 +45,7 @@ objects = $(DL_FILE)
>   
>   $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>   
> -$(DL_FILE)_MD5 = a7088cec171b0d00bf43394ce64d3909
> +$(DL_FILE)_MD5 = f294efbeabcf6027fccc7983a6daa55f
>   
>   install : $(TARGET)
>   
> 

      reply	other threads:[~2021-09-18 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 13:47 Matthias Fischer
2021-09-18 16:08 ` Peter Müller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4aaca06f-c794-c287-aa50-c5da0bfbc51d@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox