Skip to content

Netty vulnerable to HTTP Response splitting from assigning header value iterator

Moderate severity GitHub Reviewed Published Dec 12, 2022 in netty/netty • Updated Jan 29, 2023

Package

maven io.netty:netty-codec-http (Maven)

Affected versions

>= 4.1.83.Final, < 4.1.86.Final

Patched versions

4.1.86.Final

Description

Impact

When calling DefaultHttpHeaders.set with an iterator of values (as opposed to a single given value), header value validation was not performed, allowing malicious header values in the iterator to perform HTTP Response Splitting.

Patches

The necessary validation was added in Netty 4.1.86.Final.

Workarounds

Integrators can work around the issue by changing the DefaultHttpHeaders.set(CharSequence, Iterator<?>) call, into a remove() call, and call add() in a loop over the iterator of values.

References

HTTP Response Splitting
CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers

For more information

If you have any questions or comments about this advisory:

References

@normanmaurer normanmaurer published to netty/netty Dec 12, 2022
Published to the GitHub Advisory Database Dec 12, 2022
Reviewed Dec 12, 2022
Published by the National Vulnerability Database Dec 13, 2022
Last updated Jan 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.223%
(61st percentile)

Weaknesses

CVE ID

CVE-2022-41915

GHSA ID

GHSA-hh82-3pmq-7frp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.