public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Security issue in Apache 2.4.27 ("optionsbleed")
Date: Tue, 19 Sep 2017 17:14:09 +0200	[thread overview]
Message-ID: <20170919171409.4efbd4e2.peter.mueller@link38.eu> (raw)

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

Hello,

a security issue has been found in Apache 2.4.27, which is
at the moment scheduled for the "next" branch in IPFire.

It is a memory leak (called "optionsbleed"), more details
are available here:
* https://nvd.nist.gov/vuln/detail/CVE-2017-9798
* https://heise.de/-3835313 (german only)

A patch has been published on Apache's SVN repository (but
I am not sure how to add it to the LFS build file :-) ):
https://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/server/core.c?r1=1805223&r2=1807754&pathrev=1807754&view=patch

Although IPFire is not vulnerable as far as I know, it
might be good to deploy this. Affects the 2.2.x series, too.

Just in case anyone is interested.

Best regards,
Peter Müller

             reply	other threads:[~2017-09-19 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 15:14 Peter Müller [this message]
2017-09-19 17:23 ` Matthias Fischer
2017-09-20 21:12   ` Michael Tremer

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=20170919171409.4efbd4e2.peter.mueller@link38.eu \
    --to=peter.mueller@link38.eu \
    --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