dbcve.org
UndertowApplication · Redhat

CVE-2019-14888

HIGH · 7.5 CVSS v3.1 Published 2020-01-23
Fix available
A fix is available. Upgrade to after 2.0.28 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in the Undertow HTTP server in versions before 2.0.28.SP1 when listening on HTTPS. An attacker can target the HTTPS port to carry out a Denial Of Service (DOS) to make the service unavailable on SSL.

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 confidence

A Denial of Service vulnerability exists in the Undertow HTTP server in versions prior to 2.0.28.SP1 when configured to listen on HTTPS. An attacker can target the HTTPS port with malicious requests to render the SSL service unavailable.

MitigationUpgrade Undertow to version 2.0.28.SP1 or later to patch the vulnerability.

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
Affected:<= 2.0.28
Jboss Data GridApplication
Affected:all versions= 7.0.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0
Jboss FuseApplication
Affected:= 6.0.0= 7.0.0
Single Sign OnApplication
Affected:= 7.0
Active Iq Unified ManagerApplication
Affected:all versions

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Undertow presence
    Search for undertow-core JAR files or Undertow dependencies in your application's lib, WAR, or dependency manifest (pom.xml, build.gradle). Run: find . -name 'undertow*.jar' 2>/dev/null or grep -r 'undertow' pom.xml build.gradle 2>/dev/null
    Affected if Undertow JAR or dependency is found in your application
  2. Determine Undertow version
    Inspect the Undertow JAR manifest or check the dependency version in your build configuration. If using Maven, run: mvn dependency:tree | grep undertow
    Affected if The version is 2.0.28 or earlier, or the version cannot be determined and Undertow is present with HTTPS enabled
  3. Check for HTTPS connector configuration
    Examine your Undertow server configuration file (commonly undertow.xml, standalone.xml for JBoss, or programmatic XNIO configuration) for any <https> listener, SecurityRealm, or SSL/TLS configuration sections
    Affected if An HTTPS listener or SSL/TLS configuration is defined and enabled for the Undertow server
  4. Verify HTTPS port exposure
    Check your server startup scripts, configuration files, or running processes for any HTTPS port bindings (commonly port 8443 or 443) and confirm the Undertow server is listening on that port
    Affected if The server exposes an HTTPS port and Undertow handles that connection
  5. Confirm Red Hat product versions if applicable
    If using JBoss Data Grid, JBoss EAP, JBoss Fuse, or Red Hat Single Sign-On, check the product version via 'rpm -qi' or the product's version command, as these include affected Undertow versions
    Affected if Running any of the specific Red Hat product versions listed in the affected products (JDG 7.0.0, EAP 7.0.0, Fuse 6.0.0/7.0.0, RHSSO 7.0)

You are affected if Undertow version 2.0.28 or earlier is in use AND the server is configured with an active HTTPS listener on an exposed port.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.0.28
Interim mitigation

Upgrade Undertow to version 2.0.28.SP1 or later to patch the vulnerability.

Fix this in Undertow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14888 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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