CVE-2019-10212

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.

Published: 2019-10-02 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-10212 is rated Moderate Risk (61.5/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.45%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-10212

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-13 0.29% 0.45% +0.16%
2 2025-11-21 0.47% 0.29% -0.18%
3 2025-11-18 — 0.47% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10212

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
4.8 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 0.5 4.2 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-10212

GitHub Security Advisory for CVE-2019-10212

GHSA-8vh8-vc28-m2hf · Severity: critical · Ecosystem: maven — Potential to access user credentials from the log files when debug logging enabled

OS Trackers for CVE-2019-10212

vendor priority summary link
debian not yet assigned CVE-2019-10212 not yet assigned priority: Debian including 1 source packages (undertow), 2 status rows across 2 suites (forky, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2019-10212
redhat medium — https://access.redhat.com/security/cve/CVE-2019-10212
ubuntu medium CVE-2019-10212 medium priority: Ubuntu including 1 source packages (undertow), 18 status rows across 18 suites (bionic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 6, needs-triage 5, ignored 4, DNE 3. https://ubuntu.com/security/CVE-2019-10212

Affected software / configurations for CVE-2019-10212

Vendor Product Version Raw CPE
redhat undertow < 2.0.20 cpe:2.3:a:redhat:undertow:*:*:*:*:*:*:*:*
redhat jboss_data_grid >= 7.0.0, <= 7.3 cpe:2.3:a:redhat:jboss_data_grid:*:*:*:*:*:*:*:*
redhat jboss_data_grid — cpe:2.3:a:redhat:jboss_data_grid:-:*:*:*:text-only:*:*:*
redhat jboss_enterprise_application_platform — cpe:2.3:a:redhat:jboss_enterprise_application_platform:-:*:*:*:text-only:*:*:*
redhat jboss_fuse >= 7.0.0, <= 7.4 cpe:2.3:a:redhat:jboss_fuse:*:*:*:*:*:*:*:*
redhat openshift_application_runtimes — cpe:2.3:a:redhat:openshift_application_runtimes:-:*:*:*:text-only:*:*:*
redhat single_sign-on >= 7.0, <= 7.3 cpe:2.3:a:redhat:single_sign-on:*:*:*:*:*:*:*:*
netapp active_iq_unified_manager — cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:linux:*:*
netapp active_iq_unified_manager — cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:vmware_vsphere:*:*
netapp active_iq_unified_manager — cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:windows:*:*
redhat jboss_enterprise_application_platform 7.2 cpe:2.3:a:redhat:jboss_enterprise_application_platform:7.2:*:*:*:*:*:*:*
redhat jboss_enterprise_application_platform 7.3 cpe:2.3:a:redhat:jboss_enterprise_application_platform:7.3:*:*:*:*:*:*:*
redhat jboss_enterprise_application_platform 7.4 cpe:2.3:a:redhat:jboss_enterprise_application_platform:7.4:*:*:*:*:*:*:*

References for CVE-2019-10212

cvelogic Threat Intelligence