CVE-2017-12196: Incorrect Authorization in Undertow
Summary
CVE-2017-12196: Incorrect Authorization in Undertow. Affects io.undertow:undertow-core across 2 version ranges.
< 1.4.24.Final
>= 2.0.0.Alpha1, < 2.0.2.FInal
Fixed in 1.4.24.Final or 2.0.2.FInal, depending on the release line you run. How to fix ↓
Also tracked for
- undertow · Debian:13
The same CVE-2017-12196 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
Undertow is a lightweight web server written in Java that is designed to be flexible and performant. It provides a foundation for building web applications and services. Undertow supports various authentication mechanisms, including Digest authentication, which is used to verify the identity of clients. However, a vulnerability was discovered in Undertow versions 1.4.18.SP1, 2.0.2.Final, and 1.4.24.Final that allows an attacker to perform a Man-in-the-Middle (MITM) attack and access unauthorized content on the server.
Vulnerability Detail
The vulnerability arises from a failure to ensure that the value of the URI in the Authorization header matches the URI in the HTTP request line. This means that an attacker can manipulate the Authorization header to access content that they are not authorized to view. By intercepting the communication between the client and the server, the attacker can modify the URI in the Authorization header to gain unauthorized access. This can lead to the exposure of sensitive information or the ability to perform unauthorized actions on the server.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
< 1.4.24.Final1.4.24.Final -
>= 2.0.0.Alpha1, < 2.0.2.FInal2.0.2.FInal
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading to a fixed version is not immediately feasible, a possible workaround is to disable Digest authentication and use an alternative authentication mechanism that is not affected by this vulnerability. This can be done by modifying the server configuration to remove or disable the Digest authentication module.
Conclusion
The vulnerability in Undertow allows an attacker to perform a Man-in-the-Middle attack and access unauthorized content on the server. It is important to upgrade to a fixed version of Undertow or apply the recommended workaround to mitigate the risk. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for io.undertow:undertow-core →
FAQ
Undertow is a lightweight web server written in Java that provides a foundation for building web applications and services.
Digest authentication is a mechanism used to verify the identity of clients in a web server. It uses a challenge-response mechanism to authenticate clients based on a shared secret.
The vulnerability allows an attacker to perform a Man-in-the-Middle attack and access unauthorized content on the server. This can lead to the exposure of sensitive information or the ability to perform unauthorized actions.
Undertow versions 1.4.18.SP1, 2.0.2.Final, and 1.4.24.Final are affected by this vulnerability.
To fix the vulnerability, it is recommended to upgrade to Undertow versions 2.0.2.Final or 1.4.24.Final. Alternatively, you can disable Digest authentication and use an alternative authentication mechanism.
Related vulnerabilities
Recent vulnerabilities recorded for io.undertow:undertow-core.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
