From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.19 - Core Update 105 released
Date: Fri, 23 Sep 2016 17:35:54 +0100 [thread overview]
Message-ID: <mailman.799.1474649008.1498.ipfire-announce@lists.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
http://www.ipfire.org/news/ipfire-2-19-core-update-105-released
This is the official release announcement for IPFire 2.19 – Core Update 105
which patches a number of security issues in two cryptographic libaries: openssl
and libgcrypt. We recommend installing this update as soon as possible and
reboot the IPFire system to complete the update.
OpenSSL Security Fixes
* OCSP Status Request extension unbounded memory growth (CVE-2016-6304)
* SWEET32 Mitigation (CVE-2016-2183)
* OOB write in MDC2_Update() (CVE-2016-6303)
* Malformed SHA512 ticket DoS (CVE-2016-6302)
* OOB write in BN_bn2dec() (CVE-2016-2182)
* OOB read in TS_OBJ_print_bio() (CVE-2016-2180)
* Pointer arithmetic undefined behaviour (CVE-2016-2177)
* Constant time flag not preserved in DSA signing (CVE-2016-2178)
* DTLS buffered message DoS (CVE-2016-2179)
* DTLS replay protection DoS (CVE-2016-2181)
* Certificate message OOB reads (CVE-2016-6306)
IPFire is now shipping openssl in version 1.0.2i which patches all of the above
security vulnerabilities.
libgcrypt Security Flaws
Felix Dörre and Vladimir Klebanov from the Karlsruhe Institute of Technology
found a bug in the mixing functions of Libgcrypt’s random number generator: An
attacker who obtains 4640 bits from the RNG can trivially predict the next 160
bits of output. This bug exists since 1998 in all GnuPG and Libgcrypt versions
and is filed under CVE-2016-6316.
We are currently crowdfunding a Captive Portal for IPFire and would like you to
ask to check it out and support us [1]!
Please help us to support the work on IPFire Project with your donation [2].
[1] http://wishlist.ipfire.org/wish/the-ipfire-captive-portal
[2] http://www.ipfire.org/donate
reply other threads:[~2016-09-23 16:35 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.799.1474649008.1498.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