dbcve.org
UndertowApplication · Redhat

CVE-2019-3888

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-12
Fix available
A fix is available. Upgrade to 2.0.21 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Undertow web server before 2.0.21. An information exposure of plain text credentials through log files because Connectors.executeRootHandler:402 logs the HttpServerExchange object at ERROR level using UndertowLogger.REQUEST_LOGGER.undertowRequestFailed(t, exchange)

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

Undertow web server before 2.0.21 logs the HttpServerExchange object at ERROR level when request handling fails. This exposes plain-text credentials (potentially from Authorization headers or request parameters) directly into log files, allowing attackers with log access to obtain valid credentials.

MitigationUpgrade Undertow to version 2.0.21 or later, or implement log filtering to prevent credential-containing headers from being written to logs.

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.21
VirtualizationApplication
Affected:= 4.0
Virtualization HostApplication
Affected:= 4.0
Jboss Data GridApplication
Affected:all versions
Openshift Application RuntimesApplication
Affected:all versions
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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 version
    Locate the undertow-core jar file or check the Undertow version included in your Red Hat product (JBoss, Virtualization, Openshift Application Runtimes, or NetApp Active IQ Unified Manager). Use 'jar -tf' on undertow-core.jar or check your product's about/version page for the Undertow version number.
    Affected if Undertow version is below 2.0.21
  2. Confirm ERROR level logging is enabled
    Inspect your Undertow or application server logging configuration (such as logging.properties, logback.xml, or jboss-logging configuration) to verify that ERROR level logging is enabled for the Undertow HttpServerExchange handler.
    Affected if ERROR level logging for Undertow is enabled in your logging configuration
  3. Check for credential-containing requests
    Review your application to determine if it processes authentication via HTTP Authorization headers or request parameters that could contain user credentials.
    Affected if Your application processes requests with Authorization headers or credentials in query/form parameters
  4. Inspect log files for credential exposure
    Search your Undertow or application server log files for plain-text strings that resemble Basic authentication credentials (base64-encoded patterns) or credential-like parameter values appearing in ERROR level log entries.
    Affected if Log files contain Authorization header values or credential parameters in ERROR level messages

You are affected if running Undertow below version 2.0.21 with ERROR level logging enabled and your application handles credentials that could be written to logs upon request handling failures.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0.21 or later
Fixed in 2.0.21
Interim mitigation

Upgrade Undertow to version 2.0.21 or later, or implement log filtering to prevent credential-containing headers from being written to logs.

Recommended fix High confidence

Undertow 2.0.21 or later (or corresponding Red Hat security updates for bundled products)

  1. Upgrade Undertow to version 2.0.21 or later to resolve the credential logging vulnerability
  2. For Red Hat products (Virtualization 4.0, JBoss Data Grid, Openshift Application Runtimes, Active IQ Unified Manager), apply the corresponding Red Hat security errata that updates the bundled Undertow component
  3. After upgrading, verify that log files no longer contain plaintext credentials in HttpServerExchange dumps
  4. Review application logs to confirm the fix is effective and no sensitive data is being exposed
Caveat Security-focused upgrade with minimal risk; however, always test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Undertow Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3888 — 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-3888 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