Undertow HTTP2 unknown vulnerability

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability, which was classified as problematic, was found in Undertow (version unknown). Affected is an unknown code block of the component HTTP2 Handler. The manipulation with an unknown input leads to a invocation of process using visible sensitive information vulnerability. CWE is classifying the issue as CWE-214. A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system. This is going to have an impact on availability. CVE summarizes:

A flaw was found in Undertow that tripped the client-side invocation timeout with certain calls made over HTTP2. This flaw allows an attacker to carry out denial of service attacks.

The weakness was presented 08/27/2022. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2021-3859 since 10/05/2021. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Applying the patch e43f0ada3f4da6e8579e0020cec3cb1a81e487c2 is able to eliminate this problem. The bugfix is ready for download at github.com.




  • free

CPE 2.3info

CPE 2.2info


VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔒



VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍


Class: Invocation of process using visible sensitive information
CWE: CWE-214
ATT&CK: T1592

Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒


Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: e43f0ada3f4da6e8579e0020cec3cb1a81e487c2


10/05/2021 CVE reserved
08/27/2022 +326 days Advisory disclosed
08/27/2022 +0 days VulDB entry created
10/02/2022 +36 days VulDB last update


Advisory: e43f0ada3f4da6e8579e0020cec3cb1a81e487c2
Status: Confirmed

CVE: CVE-2021-3859 (🔒)


Created: 08/27/2022 08:08 AM
Updated: 10/02/2022 02:23 PM
Changes: 08/27/2022 08:08 AM (39), 10/02/2022 02:18 PM (1), 10/02/2022 02:23 PM (11)
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you know our Splunk app?

Download it now for free!