LiveActive security incident?Get immediate response
CVE Record

CVE-2019-10184: undertow before version 2.0.23.Final is vulnerable to an information leak issue.

undertow before version 2.0.23.Final is vulnerable to an information leak issue. Web apps may have their directory structures predicted through requests without trailing slashes via the api.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-10184 is an Undertow information disclosure issue. A web application using Undertow before 2.0.23.Final may reveal enough behavior for outsiders to infer directory structure when URLs omit trailing slashes. It is not described as code execution, data modification, or service outage.

Executive priority

Treat this as a medium-priority remediation item. It should be fixed during normal patch cycles, faster for externally exposed applications or products where route disclosure could aid targeted reconnaissance.

Technical view

The CVE describes Undertow before 2.0.23.Final leaking information through API handling of requests without trailing slashes. CVSS 3.0 is 5.3 with network reachability, low attack complexity, no privileges, no user interaction, and low confidentiality impact only.

Likely exposure

Exposure is most likely in internet-facing or internal Java web applications, frameworks, or products embedding Undertow versions before 2.0.23.Final. The bundle lists Red Hat and NetApp advisories, so packaged products should be checked against vendor-specific guidance.

Exploitation context

The provided bundle does not indicate CISA KEV inclusion or active exploitation. The issue appears useful for reconnaissance because it may disclose predictable application directory structure, but the sources do not support claims of direct compromise or weaponized exploitation.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, fixed version, and vendor advisories. The core impact is confidentiality loss through path-handling behavior, not integrity or availability. Product-specific reachability depends on how Undertow is embedded and exposed.

Mitigation direction

  • Upgrade Undertow to 2.0.23.Final or a later vendor-supported fixed release.
  • Apply relevant Red Hat or product vendor security advisories where Undertow is bundled.
  • Inventory applications and appliances that embed Undertow rather than declaring it directly.
  • Review vendor guidance if packaged product impact is unclear.

Validation and detection

  • Check SBOMs, dependency manifests, and runtime packages for Undertow versions before 2.0.23.Final.
  • Confirm patched deployments no longer include vulnerable Undertow artifacts.
  • Review web access logs for unusual probing of directory-like paths without trailing slashes.
  • Regression-test routing behavior without exposing directory structure details.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-10184 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
14Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.3Medium
CVSS 3.0 vector shape for CVE-2019-10184Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
undertow-ioundertowfixed in 2.0.23.FinalListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.