GHSA-cp7v-vmv7-6x2q CVE-2017-12196
Incorrect Authorization in Undertow
Medium
Maven
- Severity
- 5.9 / 10
- Medium · CVSS 3.0
- Exploit chance (EPSS)
- 2.01%
- Chance of exploitation in the next 30 days. Higher than 80.87% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-863 Incorrect Authorization
- Fix
2.0.2.FInal- Upgrade io.undertow:undertow-core to this version or later
Description
Undertow before versions 1.4.18.SP1 (not findable in Maven), 2.0.2.Final, and 1.4.24.Final was found vulnerable when using Digest authentication, the server does not ensure that the value of URI in the Authorization header matches the URI in HTTP request line. This allows the attacker to cause a MITM attack and access the desired content on the server.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| io.undertow:undertow-core | >= 2.0.0.Alpha1, < 2.0.2.FInal |
2.0.2.FInal |
| io.undertow:undertow-core | < 1.4.24.Final |
1.4.24.Final |
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.0.2.FInal
- maven
<dependency><groupId>io.undertow</groupId><artifactId>undertow-core</artifactId><version>2.0.2.FInal</version></dependency>- gradle
implementation("io.undertow:undertow-core:2.0.2.FInal")
Severity breakdown
CVSS 3.0 5.9
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-863: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How to prevent it
- Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
- System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
References
Advisories
Packages
Other links
- github.com/undertow-io/undertow/commit/facb33a5cedaf4b7b96d3840a08210370a806870
- access.redhat.com/errata/RHSA-2018:0478
- access.redhat.com/errata/RHSA-2018:0479
- access.redhat.com/errata/RHSA-2018:0480
- access.redhat.com/errata/RHSA-2018:0481
- access.redhat.com/errata/RHSA-2018:1525
- access.redhat.com/errata/RHSA-2018:2405
- access.redhat.com/errata/RHSA-2018:3768
- bugzilla.redhat.com/show_bug.cgi
- issues.jboss.org/browse/UNDERTOW-1190
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