Netty up to 4.1.41 Whitespace HTTP Request request smuggling
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Netty up to 4.1.41. This affects an unknown function of the component Whitespace Handler. The manipulation as part of HTTP Request leads to request smuggling. This vulnerability is uniquely identified as CVE-2019-16869. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Netty up to 4.1.41. This issue affects some unknown processing of the component Whitespace Handler. The manipulation as part of a HTTP Request leads to a request smuggling vulnerability. Using CWE to declare the problem leads to CWE-444. The product acts as an intermediary HTTP agent
(such as a proxy or firewall) in the data flow between two
entities such as a client and server, but it does not
interpret malformed HTTP requests or responses in ways that
are consistent with how the messages will be processed by
those entities that are at the ultimate destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Netty before 4.1.42.Final mishandles whitespace before the colon in HTTP headers (such as a "Transfer-Encoding : chunked" line), which leads to HTTP request smuggling.
The weakness was disclosed 09/26/2019 (Website). The advisory is shared at seclists.org. The identification of this vulnerability is CVE-2019-16869 since 09/25/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.1.42.Final eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2022-0770). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- IBM DB2
- Red Hat Enterprise Linux
- IBM SPSS
- EMC Avamar
- Hitachi Ops Center
Product
Name
Version
- 4.1.0
- 4.1.1
- 4.1.2
- 4.1.3
- 4.1.4
- 4.1.5
- 4.1.6
- 4.1.7
- 4.1.8
- 4.1.9
- 4.1.10
- 4.1.11
- 4.1.12
- 4.1.13
- 4.1.14
- 4.1.15
- 4.1.16
- 4.1.17
- 4.1.18
- 4.1.19
- 4.1.20
- 4.1.21
- 4.1.22
- 4.1.23
- 4.1.24
- 4.1.25
- 4.1.26
- 4.1.27
- 4.1.28
- 4.1.29
- 4.1.30
- 4.1.31
- 4.1.32
- 4.1.33
- 4.1.34
- 4.1.35
- 4.1.36
- 4.1.37
- 4.1.38
- 4.1.39
- 4.1.40
- 4.1.41
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Request smugglingCWE: CWE-444
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Netty 4.1.42.Final
Timeline
09/25/2019 🔍09/26/2019 🔍
09/27/2019 🔍
01/11/2026 🔍
Sources
Advisory: RHSA-2019:3892Status: Confirmed
CVE: CVE-2019-16869 (🔍)
GCVE (CVE): GCVE-0-2019-16869
GCVE (VulDB): GCVE-100-142337
CERT Bund: WID-SEC-2022-0770 - IBM DB2: Mehrere Schwachstellen
Entry
Created: 09/27/2019 14:32Updated: 01/11/2026 20:25
Changes: 09/27/2019 14:32 (55), 09/10/2020 14:23 (1), 12/28/2023 12:40 (4), 07/07/2025 23:24 (17), 01/11/2026 20:25 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.