From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.19 - Core Update 116 released
Date: Mon, 06 Nov 2017 21:00:14 +0000 [thread overview]
Message-ID: <mailman.73.1510002033.839.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
https://www.ipfire.org/news/ipfire-2-19-core-update-116-released
Just days after releasing Core Update 115 with our brand new Captive Portal, we
are releasing the next update for IPFire which is necessary because some
security vulneratbilities have been found in some packages that IPFire uses.
Those are openssl and wget, but this update also brings some smaller bug fixes.
To help us to provide Core Updates regularly and swiftly in case of any security
issues, we would like to ask you to support the project by sending us your
donation [1]!
openssl 1.0.2m
The OpenSSL project released version 1.0.2m and issued two security advisories
in the last week. The two vulnerabilities that were discovered were of moderate
and low security, but we have decided to ship you this update as soon as
possible. Hence it is recommended to update as soon as possible, too.
The more severe vulnerability referenced as CVE-2017-3736 fixes a problem with
modern Intel Broadwell and AMD Ryzen processors where OpenSSL uses some modern
DMI1, DMI2 and ADX extensions and calculates the square root incorrectly. This
could be exploited by an attacker who is able to put significant resources into
recover a private key more easy alas this attack is still considered virtually
unfeasible by the OpenSSL security team.
The less severe vulnerability was caused by overreading certificate data when a
certificate has a malformed IPAddressFamily extension. This could lead lead to
erroneous display of the certificate in text format. This vulnerability is
tracked under CVE-2017-3735.
Misc.
* wget also suffered from two security vulnerabilities that allowed an attacker
to execute arbitrary code. They are referenced under CVE-2017-13089 and CVE-
2017-13090.
* apache was updated to version 2.4.29 which fixes a number of bugs.
* snort has been updated to version 2.9.11.
* xz has also been updated to version 5.2.3 which brings various improvements.
It is recommended to reboot the IPFire system after installing this Core Update.
[1] http://www.ipfire.org/donate
reply other threads:[~2017-11-06 21:00 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.73.1510002033.839.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