Skip to content
Fencer Vulns
medium 4.8

CVE-2019-10212 json

Potential to access user credentials from the log files when debug logging enabled

published 2019-10-02 7 y ago modified 2026-06-17 4 mo ago also GHSA-8vh8-vc28-m2hf , EUVD-2019-0739

cvss
4.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven io.undertow:undertow-core 2.0.20
  • redhat undertow 2.0.20
  • undertow Debian 14 2.0.27-1

debian advisories DEBIAN-CVE-2019-10212

  • eap7-netty jboss enterprise application platform 7.2 4.1.34-2.Final_redhat_00002.1.el8eap
  • eap7-jgroups jboss enterprise application platform 7.2 4.0.20-1.Final_redhat_00001.1.el8eap
  • eap7-wildfly jboss enterprise application platform 7.2 7.2.4-1.GA_redhat_00002.1.el8eap
  • eap7-narayana jboss enterprise application platform 7.2 5.9.6-1.Final_redhat_00001.1.el8eap
  • eap7-undertow jboss enterprise application platform 7.2 2.0.25-1.SP1_redhat_00001.1.el8eap
  • eap7-weld-ejb jboss enterprise application platform 7.2 3.0.6-2.Final_redhat_00002.1.el8eap
  • eap7-weld-jta jboss enterprise application platform 7.2 3.0.6-2.Final_redhat_00002.1.el8eap
  • eap7-weld-web jboss enterprise application platform 7.2 3.0.6-2.Final_redhat_00002.1.el8eap

red hat advisories RHSA-2019:2937RHSA-2019:2936RHSA-2019:2935

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-10212 updated cvss 4.8

undertow: DEBUG log for io.undertow.request.security if enabled leaks credentials to log files

  • Red Hat Fuse 7 undertow undertow Red Hat JBoss Enterprise Application Platform 6 jbossweb jbossweb Red Hat JBoss Fuse 6 undertow undertow
    affected: workaround, no fix planned “Use Elytron instead of legacy Security subsystem.”
  • Red Hat OpenShift Application Runtimes undertow undertow Red Hat Single Sign-On 7 undertow undertow
    affected: workaround, no fix available “Use Elytron instead of legacy Security subsystem.”
  • Red Hat Data Grid 7.3.3
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2020:0727
  • Red Hat JBoss EAP 7.2
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2019:2938
  • Red Hat JBoss EAP 7.2 for RHEL 6 Server eap7-wildfly 7.2.4-1.GA_redhat_00002.1.el6eap, eap7-jackson-core 2.9.9-1.redhat_00001.1.el6eap, eap7-netty 4.1.34-2.Final_redhat_00002.1.el6eap, eap7-undertow 2.0.25-1.SP1_redhat_00001.1.el6eap, eap7-hibernate 5.3.11-2.SP1_redhat_00001.1.el6eap, eap7-jgroups 4.0.20-1.Final_redhat_00001.1.el6eap, +124 more
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2019:2935
  • Red Hat JBoss EAP 7.2 for RHEL 7 Server eap7-wildfly 7.2.4-1.GA_redhat_00002.1.el7eap, eap7-jackson-core 2.9.9-1.redhat_00001.1.el7eap, eap7-netty 4.1.34-2.Final_redhat_00002.1.el7eap, eap7-undertow 2.0.25-1.SP1_redhat_00001.1.el7eap, eap7-hibernate 5.3.11-2.SP1_redhat_00001.1.el7eap, eap7-jgroups 4.0.20-1.Final_redhat_00001.1.el7eap, +126 more
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2019:2936
  • Red Hat JBoss EAP 7.2 for RHEL 8 eap7-wildfly 7.2.4-1.GA_redhat_00002.1.el8eap, eap7-jackson-core 2.9.9-1.redhat_00001.1.el8eap, eap7-netty 4.1.34-2.Final_redhat_00002.1.el8eap, eap7-undertow 2.0.25-1.SP1_redhat_00001.1.el8eap, eap7-hibernate 5.3.11-2.SP1_redhat_00001.1.el8eap, eap7-jgroups 4.0.20-1.Final_redhat_00001.1.el8eap, +124 more
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2019:2937
  • Red Hat Single Sign-On 7.3.4 zip
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2019:3050
show 2 more
  • Red Hat Text-Only RHOAR
    fixed: vendor fix “Use Elytron instead of legacy Security subsystem.” RHSA-2019:2998
  • Red Hat Process Automation 7 undertow undertow
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.89% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 4.8 CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven io.undertow:undertow-core
<2.0.20
2.0.20

Affected products

  • RedHat undertow

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.