public inbox for ipfire-announce@lists.ipfire.org
 help / color / mirror / Atom feed
From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.17 - Core Update 98 released
Date: Mon, 22 Feb 2016 15:39:20 -0800	[thread overview]
Message-ID: <mailman.86.1456186810.1659.ipfire-announce@lists.ipfire.org> (raw)

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

http://www.ipfire.org/news/ipfire-2-17-core-update-98-released

Due to a recently discovered security vulnerability in glibc, we are
releasing this Core Update that contains a fix for CVE-2015-7547.


CVE-2015-7547 in glibc/getaddrinfo

The getaddrinfo() interface is glibc, the system’s main C library, is
used to resolve names into IP addresses using DNS. An attacker can
exploit the process in the system performing this request by sending a
forged reply that is too long causing a stack buffer overflow. Code can
potentially be injected and executed.

IPFire is however not directly exploitable by this vulnerability as it
is using a DNS proxy, that rejects DNS responses that are too long. So
IPFire itself and all systems on the network that use IPFire as DNS
proxy are protected by the DNS proxy. However, we decided to push out a
patch for this vulnerability as quickly as we can.

Please reboot the system after installing the update.

----

I would also like to invite you all to support our latest crowd-funding 
campaign to fund development of a Captive Portal for IPFire:

  http://wishlist.ipfire.org/wish/the-ipfire-captive-portal

Otherwise you can of course donate using the usual ways:

  http://www.ipfire.org/donate

                 reply	other threads:[~2016-02-22 23:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=mailman.86.1456186810.1659.ipfire-announce@lists.ipfire.org \
    --to=ipfire-announce@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