dbcve.org
UndertowApplication · Redhat

CVE-2019-10212

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 2.0.20 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 flaw was found in, all under 2.0.20, in the Undertow DEBUG log for io.undertow.request.security. If enabled, an attacker could abuse this flaw to obtain the user's credentials from the log files.

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 versions prior to 2.0.20 have a DEBUG logging vulnerability in the io.undertow.request.security component. When DEBUG logging is enabled, user credentials are written in plaintext to log files, allowing attackers with log file access to obtain valid credentials.

MitigationDisable DEBUG logging for the io.undertow.request.security component in the logging configuration, or upgrade to Undertow 2.0.20 or later.

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.20
Jboss Data GridApplication
Affected:>= 7.0.0, <= 7.3all versions
Jboss Enterprise Application PlatformApplication
Affected:all versions= 7.2= 7.3= 7.4
Jboss FuseApplication
Affected:>= 7.0.0, <= 7.4
Openshift Application RuntimesApplication
Affected:all versions
Single Sign OnApplication
Affected:>= 7.0, <= 7.3
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 installation
    Locate undertow-core JAR file or check Maven/Gradle dependencies for undertow version
    Affected if Undertow version is earlier than 2.0.20
  2. Verify Undertow version
    Examine the undertow-core JAR manifest or dependency management system for exact version number
    Affected if Version is below 2.0.20
  3. Check DEBUG logging for io.undertow.request.security
    Review logging configuration files (jboss-logging.xml, logback.xml, log4j.xml) for DEBUG level on io.undertow.request.security logger
    Affected if DEBUG logging is enabled for io.undertow.request.security component
  4. Inspect log files for plaintext credentials
    Search log files for patterns matching username/password or authentication credentials in plaintext
    Affected if Log files contain plaintext user credentials

User is affected if Undertow version is earlier than 2.0.20 AND DEBUG logging is enabled for the io.undertow.request.security component

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.20 or later
Fixed in 2.0.20
Interim mitigation

Disable DEBUG logging for the io.undertow.request.security component in the logging configuration, or upgrade to Undertow 2.0.20 or later.

Recommended fix High confidence

Undertow 2.0.20.Final or later; for JBoss products apply Red Hat security patches for CVE-2019-10212

  1. 1. Identify all instances of Undertow or JBoss-based applications in your environment that are affected by this vulnerability.
  2. 2. Locate the Undertow dependency in your project's build configuration (Maven pom.xml, Gradle build.gradle, or application server installation).
  3. 3. Upgrade Undertow to version 2.0.20 or later. For Maven projects, update the undertow-core dependency: <dependency><groupId>io.undertow</groupId><artifactId>undertow-core</artifactId><version>2.0.20.Final</version></dependency>
  4. 4. If using bundled JBoss application servers (JBoss EAP, JBoss Data Grid, JBoss Fuse, etc.), apply the vendor-supplied patches from Red Hat for your specific product version.
  5. 5. After upgrading, verify that the io.undertow.request.security logger is not set to DEBUG level in your logging configuration (typically log4j.xml, logging.properties, or WildFly/JBoss standalone.xml).
  6. 6. Review existing log files for any exposed credentials and rotate them if necessary.
  7. 7. Test the upgraded application in a staging environment before deploying to production.
Caveat Review release notes for Undertow 2.0.x for any breaking changes; test thoroughly in non-production 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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