HTTP Response Splitting Affecting netty-tcnative package, versions <2.0.59-150200.3.10.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.26% (65th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-NETTYTCNATIVE-5730966
  • published22 Jun 2023
  • disclosed21 Jun 2023

Introduced: 21 Jun 2023

CVE-2022-41915  (opens in a new tab)
CWE-113  (opens in a new tab)
CWE-436  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 netty-tcnative to version 2.0.59-150200.3.10.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream netty-tcnative package and not the netty-tcnative package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

Netty project is an event-driven asynchronous network application framework. Starting in version 4.1.83.Final and prior to 4.1.86.Final, when calling DefaultHttpHeadesr.set with an iterator of values, header value validation was not performed, allowing malicious header values in the iterator to perform HTTP Response Splitting. This issue has been patched in version 4.1.86.Final. Integrators can work around the issue by changing the DefaultHttpHeaders.set(CharSequence, Iterator&lt;?&gt;) call, into a remove() call, and call add() in a loop over the iterator of values.

CVSS Scores

version 3.1