Netty is an asynchronous event-driven network application framework for
rapid development of maintainable high performance protocol servers and
clients.
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Netty prior to version 4.1.71.Final skips control chars when they are present at the beginning / end of the header name. It should instead fail fast as these are not allowed by the spec and could lead to HTTP request smuggling. Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore, and therefore does not do the validation itself. Users should upgrade to version 4.1.71.Final.
Mend Note: After conducting further research, Mend has determined that all versions of netty up to version 4.1.71.Final are vulnerable to CVE-2021-43797.
CVE-2021-43797 - Medium Severity Vulnerability
Vulnerable Library - netty-codec-http-4.1.3.Final.jar
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers and clients.
Library home page: http://netty.io/
Path to dependency file: /tests/test-sessions/test-gcloud-sessions/pom.xml
Path to vulnerable library: /tests/test-sessions/test-gcloud-sessions/pom.xml,/jetty-gcloud/jetty-gcloud-session-manager/pom.xml
Dependency Hierarchy: - google-cloud-datastore-1.0.0.jar (Root Library) - datastore-v1-protos-1.3.0.jar - grpc-google-common-protos-0.1.0.jar - grpc-all-1.0.1.jar - grpc-netty-1.0.1.jar - netty-codec-http2-4.1.3.Final.jar - :x: **netty-codec-http-4.1.3.Final.jar** (Vulnerable Library)
Found in HEAD commit: b976400adf459c779b88fa83118b68aa39af14c7
Found in base branch: main
Vulnerability Details
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Netty prior to version 4.1.71.Final skips control chars when they are present at the beginning / end of the header name. It should instead fail fast as these are not allowed by the spec and could lead to HTTP request smuggling. Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore, and therefore does not do the validation itself. Users should upgrade to version 4.1.71.Final. Mend Note: After conducting further research, Mend has determined that all versions of netty up to version 4.1.71.Final are vulnerable to CVE-2021-43797.
Publish Date: 2021-12-09
URL: CVE-2021-43797
CVSS 3 Score Details (6.5)
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: CVE-2021-43797
Release Date: 2021-12-09
Fix Resolution (io.netty:netty-codec-http): 4.1.71.Final
Direct dependency fix Resolution (com.google.cloud:google-cloud-datastore): 1.13.0
Step up your Open Source Security Game with Mend here