Bug 1343616 (CVE-2016-4970) - CVE-2016-4970 netty: Infinite loop vulnerability when handling renegotiation using SslProvider.OpenSsl
Summary: CVE-2016-4970 netty: Infinite loop vulnerability when handling renegotiation ...
Status: NEW
Alias: CVE-2016-4970
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20160607,repor...
Keywords: Security
Depends On: 1347057 1347058 1347059 1347497
Blocks: 1343619 1357951 1357954 1379523 1381801 1439275
TreeView+ depends on / blocked
 
Reported: 2016-06-07 14:28 UTC by Adam Mariš
Modified: 2019-06-08 21:16 UTC (History)
68 users (show)

(edit)
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).
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)


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 20:23:10 UTC

Description Adam Mariš 2016-06-07 14:28:12 UTC
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 05:08:06 UTC
Created netty tracking bugs for this issue:

Affects: fedora-all [bug 1347497]

Comment 10 Tomas Hoger 2016-06-28 11:09:32 UTC
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 11:16:52 UTC
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 16:23:26 UTC
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.