CVE-2016-4970: Loop with Unreachable Exit Condition in Netty

CVE-2016-4970 · Severity: low · CVSS 3.1 · Published 2022-05-13

Loop with Unreachable Exit Condition in Netty

Technologies: io.netty:netty-handler (Maven). Vendors: Maven.

Quick answers

Is CVE-2016-4970 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-4970 being exploited in the wild.
How severe is CVE-2016-4970?
Low severity, with a CVSS score of 3.1, published 13 May 2022.
Which products and versions are affected?
io.netty:netty-handler (Maven) ECOSYSTEM:introduced=4.0.0.Alpha1,fixed=4.0.37.Final.
Is there a fix for CVE-2016-4970?
Yes. io.netty:netty-handler (Maven): upgrade to 4.0.37.Final or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2016-4970?
Check whether you run io.netty:netty-handler (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • io.netty:netty-handler (Maven): upgrade to 4.0.37.Final or later
    # set io.netty:netty-handler to 4.0.37.Final in your pom.xml or build.gradle

Affected products

  • io.netty:netty-handler (Maven) ECOSYSTEM:introduced=4.0.0.Alpha1,fixed=4.0.37.Final

Identifiers

  • CVE-2016-4970
  • GHSA-rv63-gqm8-9w8q

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.