GHSA-339q-62wm-c39w CVE-2021-3859
Undertow vulnerable to Denial of Service (DoS) attacks
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.74%
- Chance of exploitation in the next 30 days. Higher than 77.68% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-214 Invocation of Process Using Visible Sensitive Information
- CWE-400 Uncontrolled Resource Consumption
- CWE-668 Exposure of Resource to Wrong Sphere
- Fix
2.2.15- Upgrade io.undertow:undertow-core to this version or later
Description
Undertow client side invocation timeout raised when calling over HTTP2, this vulnerability can allow attacker to carry out denial of service (DoS) attacks in versions less than 2.2.15 Final.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| io.undertow:undertow-core | < 2.2.15 |
2.2.15 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
io.undertow:undertow-core Maven → 2.2.15
- maven
<dependency><groupId>io.undertow</groupId><artifactId>undertow-core</artifactId><version>2.2.15</version></dependency>- gradle
implementation("io.undertow:undertow-core:2.2.15")
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-214: Invocation of Process Using Visible Sensitive Information
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.
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
CWE-668: Exposure of Resource to Wrong Sphere
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
References
Advisories
Packages
Other links
- github.com/undertow-io/undertow/pull/1296
- github.com/undertow-io/undertow/commit/db0f5be43f8e2a4b88fbedd2eb6d5a95a29ceaa8
- github.com/undertow-io/undertow/commit/e43f0ada3f4da6e8579e0020cec3cb1a81e487c2
- access.redhat.com/security/cve/cve-2021-3859
- bugzilla.redhat.com/show_bug.cgi
- issues.redhat.com/browse/UNDERTOW-1979
- security.netapp.com/advisory/ntap-20221201-0004
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-3x3v-w654-m28m Undertow: Denial of Service via Multipart/Form-Data Parsing on HTTP GET Requests | Medium | Also affects io.undertow:undertow-core |
| GHSA-33hj-rcmx-86mv Undertow Servlets Vulnerable to Remote DoS via OutOfMemoryError when Passed Large Parameter Names | High | Also affects io.undertow:undertow-core |
| GHSA-j382-5jj3-vw4j Undertow HTTP server core doesn't properly validate the Host header in incoming HTTP requests | Critical | Also affects io.undertow:undertow-core |
| GHSA-6h4f-pj3g-q8fq Undertow OutOfMemory when parsing form data encoding with application/x-www-form-urlencoded | High | Also affects io.undertow:undertow-core |
| GHSA-95h4-w6j8-2rp8 Undertow MadeYouReset HTTP/2 DDoS Vulnerability | High | Also affects io.undertow:undertow-core |
| GHSA-3jrv-jgp8-45v3 Undertow incorrectly parses cookies | High | Also affects io.undertow:undertow-core |
| GHSA-97cq-f4jm-mv8h Undertow Denial of Service vulnerability | High | Also affects io.undertow:undertow-core |
| GHSA-9623-mqmm-5rcf Undertow vulnerable to Race Condition | High | Also affects io.undertow:undertow-core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor