Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 1343616 - (CVE-2016-4970) CVE-2016-4970 netty: Infinite loop vulnerability when handling renegotiation using SslProvider.OpenSsl
CVE-2016-4970 netty: Infinite loop vulnerability when handling renegotiation ...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20160607,repor...
: Security
Depends On: 1347057 1347058 1347059 1347497
Blocks: 1343619 1357951 1357954 1379523 1381801 1439275
  Show dependency tree / graph
 
Reported: 2016-06-07 10:28 EDT by Adam Mariš
Modified: 2018-05-10 14:16 EDT (History)
70 users (show)

See Also:
Fixed In Version: netty 4.0.37, netty 4.1.1
Doc Type: Bug Fix
Doc Text:
An infinite-loop vulnerability was discovered in Netty's OpenSslEngine handling of renegotiation. An attacker could exploit this flaw to cause a denial of service. Note: Netty is only vulnerable if renegotiation is enabled (default setting).
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1097 normal SHIPPED_LIVE Moderate: Red Hat JBoss Data Grid 7.1 2017-04-19 16:23:10 EDT

  None (edit)
Description Adam Mariš 2016-06-07 10:28:12 EDT 
Due to a bug in handling return code from openssl native calls, the SslHandler that uses OpenSslEngine can end up in an infinite loop and eat up all CPU cycles, which may lead to DoS of the system.

This can only happen if the server has renegotiation enabled (which is set as default). Only systems using SslProvider.OpenSsl are affected, that will be true if netty-tcnative is in the classpath and openssl is installed.

If netty-tcnative is linked against boringssl, the problem does not exist, since renegotiation is not supported in boringssl.

Versions affected: Netty 4.0.0.Final - 4.0.36.Final and 4.1.0.Final

Workaround:

Users can use -Djdk.tls.rejectClientInitiatedRenegotiation=true to disable renegotiation and avoid this issue.
Comment 5 Summer Long 2016-06-17 01:08:06 EDT 
Created netty tracking bugs for this issue:

Affects: fedora-all [bug 1347497]
Comment 10 Tomas Hoger 2016-06-28 07:09:32 EDT 
There are 3 netty versions in Red Hat Software Collections and Red Hat Developer Toolset:

- rh-java-common-netty and devtoolset-4-netty - both used on upstream version 4.0.28.  However, OpenSslEngine is removed from those packages, similar to netty packages in Fedora:

http://pkgs.fedoraproject.org/cgit/rpms/netty.git/tree/npn_alpn_ssl_fixes.patch

- thermostat1-netty - based on upstream version 3.6.3, which does not include OpenSslEngine, which was only added upstream in version 3.9.2:

http://netty.io/news/2014/06/11/3-9-2-Final.html

Additionally, netty-tcnative required by OpenSslEngine is not shipped as part of RHSCL or DTS.
Comment 11 Tomas Hoger 2016-06-28 07:16:52 EDT 
Fedora also includes netty3 packages, using upstream version 3.9.3, and hence including OpenSslEngine.  The information above suggests only 4.0.0 and later were affected by this issue, but, based on a quick look at the code and patch, it's not obvious to me why 3.9.x are not affected.  CCing netty3 packages owner so that they can be double checked.
Comment 16 errata-xmlrpc 2017-04-19 12:23:26 EDT 
This issue has been addressed in the following products:



Via RHSA-2017:1097 https://access.redhat.com/errata/RHSA-2017:1097
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.