UndertowApplication · Redhat
CVE-2017-12196
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedundertow before versions 1.4.18.SP1, 2.0.2.Final, 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUndertow before versions 1.4.18.SP1, 2.0.2.Final, and 1.4.24.Final contains an authentication bypass vulnerability in its HTTP Digest authentication implementation. The server fails to validate that the URI in the Authorization header matches the URI in the HTTP request line, allowing an attacker performing a man-in-the-middle (MITM) attack to access protected resources by manipulating the URI in the Authorization header.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
UndertowApplication
<= 1.4.18= 1.4.24= 2.0.2
Jboss Enterprise Application PlatformApplication
= 7.0.0
Jboss FuseApplication
= 6.0.0
VirtualizationApplication
= 4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Undertow is in useSearch for undertow-core.jar or undertow-servlet.jar in the application deployment, or check for undertow dependencies in pom.xml or build.gradle. If using JBoss EAP, JBoss Fuse, or Red Hat Virtualization, Undertow may be embedded.Affected if Undertow or a Red Hat product containing Undertow is deployed
-
Determine Undertow versionCheck the MANIFEST.MF file inside the undertow-core.jar for Implementation-Version, or examine the pom.xml if Undertow is a project dependency. For JBoss EAP, check the jboss-as-server manifest or run 'rpm -qi jbossas-core' or check the installed product version.Affected if The version falls within <= 1.4.18, = 1.4.24, = 2.0.2 for Undertow, or = 7.0.0 for JBoss EAP, = 6.0.0 for JBoss Fuse, = 4.0 for Virtualization
-
Identify if HTTP Digest authentication is configuredReview web.xml deployment descriptors for <auth-method>DIGEST</auth-method> in <login-config> sections, or check undertow's handler configuration files for DigestAuthenticationMechanism. Also review any custom SecurityRealm or IdentityManager configuration using digest authentication.Affected if HTTP Digest authentication is enabled as the authentication method in the deployment configuration
A user is affected if they are running a vulnerable Undertow version (or vulnerable JBoss EAP/Fuse/Virtualization version) with HTTP Digest authentication enabled, allowing potential URI manipulation in the Authorization header during MITM attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Undertow to version 1.4.18.SP1, 2.0.2.Final, 1.4.24.Final or later. If upgrading is not immediately possible, avoid using Digest authentication until the patch can be applied.
Fix this in Undertow
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12196 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data